No way to keep the browser open for nested SSO with authenticator app

[maksymtrilenko]

Flow:

1. The Flutter app opens the IDP authenticate url in a Chrome Custom Tab.
2. The user presses the one tap login button which opens the authenticator app (using a custom scheme) where the user approves the sign in request
3. The authenticator app calls the Flutter app's callback scheme
4. The IDP page inside the Chrome Custom Tab activity checks periodically whether the login is approved to execute a callback with the 'code' parameter

Request: The in app browser activity should remain open within (on top of?) the Flutter app not only until the app receives any callback, but until a specific parameter (code) is present in the callback.

[LinusU]

Hmm, this feels like it might be a bit out of scope for this plugin. Do you have a suggestion on how the API would look?

[maksymtrilenko]

Well, it sort of works with a few adjustments to the Android code. The main issue now is that an external Chrome Custom Tab activity is created in the app switcher every single time instead of an overlay inside the Flutter app.