This repository has been archived by the owner on Dec 1, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Fix IllegalStateException does not have a NavController set #2
Comments
VictorAlbertos
added a commit
that referenced
this issue
Jul 1, 2020
VictorAlbertos
added a commit
that referenced
this issue
Jul 1, 2020
VictorAlbertos
added a commit
that referenced
this issue
Jul 1, 2020
VictorAlbertos
added a commit
that referenced
this issue
Jul 1, 2020
VictorAlbertos
added a commit
that referenced
this issue
Jul 2, 2020
[#2] Add LenientNavHostFragment
@VictorAlbertos I tried to replace
There is no crash. Could you please provide more detailed steps to repro it? Is it easily reproducible or it's device specific? |
We were not able to replicate the issue using the Watson sample app, only happened in the Cookpad Android app. And sadly we were not able to spot the actual cause of this issue 🤷 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After bumping the navigation lib version to 2.3.0 our deep links stoped to work: when the user left the app on the background (by clicking the home button for instance) and a deep link was launched, the app crashed:
We were not able to find the actual issue and the only way we found to bypass this limitation has been subclassing NavHostFragment to try/catch the call to super::onDestroyView and sallow this particular exception. We will keep this issue open to keep track of it hoping that future versions of the navigation library fix the issue in the same way it appeared: without knowing how.
The text was updated successfully, but these errors were encountered: