Fixed
Status Update
Comments
il...@google.com <il...@google.com>
il...@google.com <il...@google.com> #2
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?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
il...@google.com <il...@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.
Description
Component used: Navigation Safe Args Kotlin Plugin
Version used: 2.4.0-alpha02, AGP 4.2.0-beta03
After upgrading to Navigation 2.4.0-alpha02 and building a minified version of my app , my app crashed with an exception that said that the
fromBundle
method couldn't be found.I use the
by navArgs()
extension, which uses reflection to access this method, so I depended on Navigation's included ProGuard keep rules to properly keep that method.I found that I could work around this issue via this commit :
Essentially just making sure that the
Companion
class is kept. After adding that ProGuard rule, thefromBundle()
class was successfully kept. I'm not sure why that helped, since I'm pretty sure that the format of thefromBundle()
didn't change since Navigation 2.3.5?Reproduction steps:
minifyEnabled true
to the./gradlew assembleDebug
and analyze the resulting APK to verify that theChooseProviderFragmentArgs.fromBundle()
method exists (it won't) 4a) Alternatively, install Muzei, Activate it as your wallpaper, then select the 'Sources' screen. Muzei should not crash.