-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Implement Authentication Flow using Deep Linking for ChromeSafariBrowser #1696
Comments
NOTE: This comment is auto-generated. Are you sure you have already searched for the same problem? Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem! If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue. In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding Following these steps can save you, me, and other people a lot of time, thanks! |
@jonasblendstrup Deep linking is not related to this package and you should implement it yourself: https://docs.flutter.dev/ui/navigation/deep-linking It is highly recommended to use the Navigator 2.0 in combination with dedicated packages like go_router for this, as deep linking then comes almost for free. |
This issue is stale and has been automatically closed because it has been open for more than 365 days with no activity. Please reopen a new issue if you still have it. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue. |
Environment
Flutter version: 3.10.5
Plugin version: 6.0.0-beta.24+1
Android version: 13
iOS version: 16.5
Xcode version: 14.3.1
Device information: -
Description
What you'd like to happen:
In issues #349, #401, and #699 @pichillilorenzo mentioned the need for implementing authentication flow using deep linking for ChromeSafariBrowser, which would allow developers to receive data from the Custom Chrome Tab / SFSafariViewController. This could solve quite a few issues, considering the amount of issues posted about the need for knowing the url's in a ChromeSafariBrowser (eg. aforementioned issues, as well as #1613, #1443, #1047).
Alternatives you've considered:
The package Flutter Web Auth 2 (https://pub.dev/packages/flutter_web_auth_2) allows giving a callback scheme, which may be used to return data from the opened Custom Chrome Tab. However this package doesn't use SFSafariViewController on iOS, it doesn't allow any customisation of the browser opened (such as colors), and it has other problems that could be solved using flutter_inappwebview's implementation of ChromeSafariBrowser.
The text was updated successfully, but these errors were encountered: