Fixed
Status Update
Comments
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.
jb...@google.com <jb...@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 Version used: 2.3.3 Devices/Android versions reproduced on: Pixel 3a
Hi all,
When the app is launched by a deep link, we are able to retrieve that deep link from the destination fragment using NavController.KEY_DEEP_LINK_INTENT . We have a widget where we pull the next destination as a deep link from a CMS system that the marketing team is able change on the fly. We would like to get the deep link from the destination fragment when launched internally as well.