Others having issue with custom tab and app links in Chrome 112.x.x.x?

[yberstad]

Configuration

• Version: 0.11.1
• Integration: ReactNative (react-native-app-auth v.7.0.0-rc2)
• Identity provider: Identity Server 6

Description

After installing Chrome version 112.x.x.x, we no longer get back to our app, using custom tab and app link:
com.app.auth://signin-oidc (example url)

If I install the 111.x.x.x version of Chrome everything works fine. Same if I set Firefox as the default browser.

Has anyone else experienced the same issue? We experience this on various devices and Android versions.

Teste on Android 12 and Android 13.

We also have several customers reporting the same.

How to install other versions of Chrome:
https://droidwin.com/how-to-downgrade-google-chrome-on-android-2-methods/

Various Chrome APK versions:
https://chrome.en.uptodown.com/android/versions

[carstenhag]

Are you getting a dialog shown like this one? I am also curious why this is happening, I guess it's a security "feature" introduced by Chrome.

It says: Continue with $appname? - This website wants to open $appname

[agologan]

Having tested this on 114.0.5735.196 both with AppLinks and custom scheme worked as expected.

Did notice if the user is being auto-logged in (having already logged into the host domain via the browser or another app), if the IdP does not have a manual confirmation step they'll get stuck in the browser.

This is something we have long commented on and most IdP have added an account selection step or consent screen as part of the flow to get that user interaction and provide better UX.

[KamenGoranchev]

@agologan Can you please explain what changed in the way how chrome is processing the redirects I have the case with the auto-login working on some versions of Chrome and on the version you mentioned (114.0.5735.196) I experience the same problem you explained with getting stuck in the browser.

[tomrader]

Redirects via app links are definitely not working properly when the browser used for auth is not the customer's default. Not 100 how to workaround that.

[ajbeaven]

We're having the same problem in Android 15. We did not experience this in previous versions of Android, so guessing it may be a recent change.

After the user logs in (via Custom Chrome Tabs), app attempts to redirect them back to the native app. They're greeted with the following dialog:

If you click "Stay in Microsoft Edge" you get stuck and cannot proceed.

Preferably the dialog could be avoided. The ChatGPT app uses Custom Chrome Tabs (or some browser-based solution) for auth but manages to redirect back post login without seeing this same dialog, so there's got to be a workaround somewhere.