Make androidx.wear.compose.material.Colors more customizable [199754668]

Fixed

Bug

Status Update

No update yet.

Description

th...@gmail.com

created issue #1

Sep 14, 2021 10:49AM

Component used: androidx.wear.compose:compose-material

Version used: 1.0.0-SNAPSHOT, build 7723219

Devices/Android versions reproduced on: all

Is there a reason that androidx.wear.compose.material.Colors is so limited? I cannot find a way to change for example the background, surface, or onSurfaceVariantX colors.

The Android developers site mentions the following: “You can customize all of these colors for your app.“ https://developer.android.com/training/wearables/design/color

I know that in the past there were lots of Wear apps with colored background (including some Google apps, and my production app). Also the system itself had colored background on multiple places.

The Android developers site has some Wear screenshots with colored backgrounds: https://developer.android.com/training/wearables/data/network-access#user-interface-considerations

It would be great if all the colors could be changed.

Comments

jn...@google.com <jn...@google.com> Sep 16, 2021 11:17AM

Reassigned to ai...@google.com.

jn...@google.com <jn...@google.com> #2Oct 7, 2021 12:31PM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

jn...@google.com <jn...@google.com> #3Oct 7, 2021 12:31PM

Reassigned to jn...@google.com.

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

ap...@google.com <ap...@google.com> #4Oct 11, 2021 04:36PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

jn...@google.com <jn...@google.com> Oct 11, 2021 05:09PM

Accepted by jn...@google.com.

jn...@google.com <jn...@google.com> #5Oct 12, 2021 11:24AM

Marked as fixed.

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

Issue 199754668