You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why still listening on Linking in Android? Because in Android, we have a can't login button
If succeed to login, it will,
jump to the schema, gitpoint://welcome, which means the welcome screen
trigger onNavigationStateChange to get the auth, and navigate to Main
I guess the stack navigator guarantees the main screen will always on the top of the welcome screen.
Problem
I tested different versions of codes and found that starting from #883, with RN 0.59,
In iOS, onNavigationStateChange is not triggered for the schema
In Android, every onNavigationStateChange is triggered but Main can't cover Welcome
Users will be blocked by the welcome screen after login in. The workaround is killing the app and open again. It has logged in so will navigate to the main screen at the second time.
Related
No tag for v1.6.0, according to translation texts, it should be > 1716618 and < ecb61fa
Backgrounds
The current designed login process,
onNavigationStateChangeLinkingin Android andreact-native-safari-viewin iOS, then listen on Linking in both platformscan't loginbuttongitpoint://welcome, which means the welcome screenMainI guess the stack navigator guarantees the main screen will always on the top of the welcome screen.
Problem
I tested different versions of codes and found that starting from #883, with RN 0.59,
Users will be blocked by the welcome screen after login in. The workaround is killing the app and open again. It has logged in so will navigate to the main screen at the second time.
Related
Welcomebe able to navigate toMain(35e4a08)Future direction should be replacing the WebView login with native implementations.