-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forceCloseOnRedirection don't work as expected #26
Comments
@maestor check this discussion ant let me know droibit/react-native-custom-tabs#11 |
any pull request to improve the README is always welcome my friend! 👍 |
yeah I have read this, but that doesn't explain why this library's custom tabs will close automatically when app go to background and forceCloseOnRedirection have set to about README and settings part, I can try improving some day, but first have to find some time for researching what all those settings exactly do. |
The README was updated :) |
Hi, |
Are you reopening the app by pressing app icon? |
I had mystery problem than Custom Tabs closing automatically if I go to other app. Notice that I had forceCloseOnRedirection value set to
true
. Actually there is two issues:forceCloseOnRedirection boolean undefined Workaround that Custom Tabs doesn't close on redirecting back to app scheme.
That said, force close should happen only if coming back to app from for example oauth registeration flow, not all the time if you go somewhere else from active browser window. Also if you have open link and open active app listing, it shows that inAppBrowser as weird new screen (Honor 9, Android 8) which you can't choose because it disappears. So setting is currently useless (didn't test yet what happens after some redirection if this is set to
false
, could be that there is no need for keep that at all?).EDIT: Tested one flow with redirection back to app, and for me application opened (and custom tabs closed) succesfully also with forceCloseOnRedirection
false
, maybe that's unrelevant and confusing setting?The text was updated successfully, but these errors were encountered: