"react-native-navigation": "^2.0.0-experimental.133"
In order to use Auth0lock for login and profile creation a single screen app is started which on login, should call startTabBasedApp and transition to tabbed app. What I am seeing is that auth0 view is popped and I am left in my single screen app root. Log suggests that the app is started. Reloading works as expected, but at that point I never go to Auth0lock view. Any suggestions?
Related
I am using branch io to implement deep linking in our react native app. I am able to navigate to different screens using the deep link from push notification when the app is in background state .
The issue occurs when app is started from fresh state. We have a Splash screen that is the default screen that loads after app starts and some logic is written in it like initializing app location ,verifying the jwt token is valid. Setting app localizations.
After these actions we navigate user to the home screen. In case of using deep link to fresh start the app it skips the Splash screen and navigates straight to the specific screen and in the result the actions we have to perform on Splash screen get skipped.
Please suggest a way to deal with this issue.
Am totally stuck with something. Working on deep link and its redirection. When clicking on a deep link it's getting redirected to my app. I have added the code to handle in my HomePage.js.
Scenario 1:
If app is removed from background in phone then the deep link redirection works great
Scenario 2:
If app is kept at HomePage.js and left in background of device. then on deep link click opens the app no redirection happens.
Scenario 3:
If app is kept at HomePage.js which have AppState.addListener() and left at background and then on click of deep link HomePage state change listener is hit but there is no url.
Expected behaviour
App should detect its being redirected when its on any page with the url.
On some app page, I call
Linking.openURL('app-settings:1')
To open the Settings app to allow someone to give me access to the Camera if they have not already.
When I change a setting, the app refreshes, and pulls up the initial/start screen.
Is this standard behavior? Can I stop the refresh?
Is there a way to listen to the change-in-permissions without modifying a Redux state, and redirect to different pages if the permission was granted/not granted?
My project includes the firebase sign-in methods: Twitter, Facebook, Google and Github.
I am using firebase.auth().signInWithPopup() to handle authentication and callback. It works fine when run in the browser:
in mobile, this is different. I realize that it opens a new safari window, but it does not redirect to the app home screen. How can we do that?
this is the project in the firebase console for the Facebook sign-in
I believe this is a known issue for home screen apps in iOS. The window that is opened is sandboxed from the home screen app. The popup is unable to pass back the result to the parent home screen app. Instead, you should use signInWithRedirect in that mode. I believe that should work.
I have developed a Worklight application in Dojo for BlackBerry OS 10.
When I click the "Reload" button, the WL.Client.reloadApp() API method is invoked.
The app gets reloaded with white screen.
I have attached the screenshots which will explain the issue.
IMO this is the expected behavior.
When using WL.Client.reloadApp() you essentially request to reload the web resources of the application; you can't expect to both show them and reload them at the same time. Thus, this is the expected behavior and the same will also happen when previewing via Worklight Console's MBS (I've checked that).
A question to ask is, why would you want to have such a button in your application to reload the app... Your scenario is unclear to me.
What you can do perhaps, is display some image while reloading using the Cordova Splashscreen API. Something like this:
function reload() {
navigator.splashscreen.show();
WL.Client.reloadApp();
}
This way when executing this function a splash will be displayed, masking the "white screen".
Next, after the app inits, you'll need to remove the splash...
So in wlCommonInit() you'll do:
function wlCommonInit() {
navigator.splashscreen.hide();
...
...
}
This should not interfere with the splash image shown by the Worklight framework upon application startup.
Try it.