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
In our app, we check whether the user is already logged in or not on App Startup. If the user is already logged in, then we redirect him to the Dashboard screen of our app, otherwise we redirect him to the login screen. We used to perform this check in APP_INITIALIZER.
But after upgrading to NativeScript v4.2 and NativeScript-Angular v6.1.0, the redirection to a correct screen has stopped working using APP_INITIALIZER. It simply shows a white screen. The sample code can be found on the following URL: https://play.nativescript.org/?template=play-ng&id=Z16l6O&v=6
Can you please check and let us know whether the latest version supports navigation using APP_INITIALIZER or not? If not, then which alternative should we use to redirect the user to an appropriate screen after app startup?
Thanks in anticipation...
Regards,
Disha.
The text was updated successfully, but these errors were encountered:
Hello, tsonevn
We can not use any delayed promises in our APP_INITIALIZER, we just simply need to route to a particular page based on user login or not. So,this issue is still open, can you please refer it once properly.
Hello,
In our app, we check whether the user is already logged in or not on App Startup. If the user is already logged in, then we redirect him to the Dashboard screen of our app, otherwise we redirect him to the login screen. We used to perform this check in APP_INITIALIZER.
But after upgrading to NativeScript v4.2 and NativeScript-Angular v6.1.0, the redirection to a correct screen has stopped working using APP_INITIALIZER. It simply shows a white screen. The sample code can be found on the following URL:
https://play.nativescript.org/?template=play-ng&id=Z16l6O&v=6
Can you please check and let us know whether the latest version supports navigation using APP_INITIALIZER or not? If not, then which alternative should we use to redirect the user to an appropriate screen after app startup?
Thanks in anticipation...
Regards,
Disha.
The text was updated successfully, but these errors were encountered: