Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
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?
jb...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
pr...@google.com
-
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
Version used: 2.4.0 through 2.5.3 (doesn't happen on 2.3.5)
Devices/Android versions reproduced on: Intel mac, M1 mac, AS Dolphin 2021.3.1 Patch 1
When using defining a safeArgs fragment argument, if the arguement matches these conditions, then you recieve a compilation error:
1. Argument is an array of a parcelable data object defined in the project.
2. Argument has a name witha character length of 19 characters.
Compilation error:
Function invocation 'map(...)' expected
Reason for error:
Generated file MyClassFragmentArgs with generated function fromSavedStateHandle. The code style wraps the generated code (maybe 100 characters as standard) splitting map function invocation "map {" over two lines.
Note:
Changing wrapping for code locally in AS does not change generated file line wrapping. Assume this is caused by some code styling shipped with dependency.
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).