Status Update
Comments
so...@google.com <so...@google.com>
an...@google.com <an...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
ma...@n26.com <ma...@n26.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
an...@google.com <an...@google.com> #4
-
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.
ap...@google.com <ap...@google.com> #5
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.
Description
Android Studio Build: `#AI-202.7319.50.2031.7019041, built on December 8, 2020`
Steps to Reproduce:
1. Create a `@Composable` function;
2. Try to access the current `Ambient*` objects;
3. Verify there's currently no `Ambient` for `SavedStateRegistryOwner`.
Given that there's already one `Ambient` for `LifecycleOwner` and `ViewModelStoreOwner`, it would be useful to have one for `SavedStateRegistryOwner` as well as we can't use `AmbientUiSavedStateOwner` as a replacement for current Android APIs neither.