iOS Deeplink - Handling asynchronous deep link #2078
Unanswered
guillaumeboussion
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey,
Did anybody here struggle with iOS asynchronous deep linking when app is in terminated state ?
Meaning that, because the app first launch to "/", you make all the initialization process (we do it through a splash screen, that triggers a lot of data fetching in a
SplashProvider
, then pushes to eitherHomeRoute
orLoginRoute
). So, imagine the process :SplashRoute
, running its data fetching throughSplashProvider
SplashProvider
implementation either didn't finish its process, or has not started yetSplashRoute
before redirecting (if you set a guard in front of yourBookRoute
)Did anybody encountered such a case ? I thought of making the
InitializationState
aStream
, so that thedeepLinkBuilder
can listen to it, and redirect onceInitializationState
isInitializationSuccess
. But maybe there's side effects to it that I don't think of..Thanks to anyone helping with this !
Beta Was this translation helpful? Give feedback.
All reactions