Ensure Android deep links are only launched once and don't make the app crash #312
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
intent.data
after being re-created which causes the initial deep link to be launched again, even after the user navigates away to another screen or if another deep link has been received in the meantime. To avoid this, returnnull
as deep link whensavedInstanceState
is non-null after re-creation.addOnNewIntentListener()
is called during each recomposition but the listener is never unregistered which can cause a leak and multiple navigator calls. To avoid this and make the code cleaner, use theproduceState()
function to encapsulate alldeeplink
state logic and unregister the listener inawaitDispose {}
.IllegalStateException
thrown byNavigator.navigate(url)
when the url doesn't match any route.