0

I have implemented login using ChromeCustomTabsBrowser. After successful login, if app's Open Supported links setting is set to "Ask evety time" instead of "Open in this app", response is not getting back to the app and showing 404 screen as attached in screen.

enter image description here

Daxa Varsani
  • 156
  • 2
  • 9

1 Answers1

0

Interesting - looks like you are using an https scheme for redirects and here is how we'd like the technology to work:

  • You are automatically deep linked back to your app when a login response is received over the https URL.

However, in practice I believe this is what happens:

  • Almost all mobile browsers try to run an internet hosted web page instead

A claimed https scheme solution is very hard to achieve and rarely used in practice today - more of an aspiration than a reality? But I believe it would need to work like this:

  • Capture the response on the internet web page which runs on your mobile device
  • Then deep link back to the app

A similar approach is used by a sample internet web page of mine - do a view source to see the logic

If it helps I have a demo Android sample that instead uses the more mainstream option of private URI schemes - though I may update it to claimed https schemes one of these days.

Even getting this form of Chrome Custom Tab based login working was a struggle, and my posts have some lessons learned that may be useful.

Gary Archer
  • 22,534
  • 2
  • 12
  • 24