Deeplinking doesn't work in UCBroswer

[shahmharsh]

We have been using the AppAuth library for our OIDC implementation. Recently we encountered an issue where when the sign in flow happens via UCBrowser, it does not deeplink back into the app. It seems like a UCBroswer issue, but wondering if anyone has encountered it, and looking for suggestions on how to tackle this issue.

Side notes:

1. To make sign in happen via UCBrowser, make it the default browser app and disable chrome
2. We are using custom schemes for deeplinking
3. This is an issue because UCBroswer is a very popular browser specially in Asian countries

[martijnvp]

Same issue here. We are using custom URI's as redirects and in a few browsers (UC, QQ, MI, Huawei, ...) web2app redirection is not happening. Users stay in the browser on receiving the authorization response with custom URI redirect.

This issue does not occur on the same devices/OS's in for instance Chrome.
We also found that AppAuth-Android/custom URI's/web2app redirection is not impossible in UC, QQ, MI, Huawei because we could get it to work with AppAuth-Android when tested against Google as OpenID Provider.
So far we are not able to determine the root cause by comparing both OpenID providers.

Does anyone have a suggestion for a solution or a way to debug this?
Also, does anyone know of certain browser-specific constraints that need to be met in order for the web2app redirection to work in these browsers?

Thanks.