Add option to disable launching authentication url in custom tabs

[bennycao]

Checklist

• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

When using web browser to authenticate, some browsers such as Vivo Browser fail to execute a callback to the app and therefore authentication fails and user cannot sign in. This is an issue as it is a widely used browser in one of our app markets.
What we have discovered is if you open the authentication url in the standalone browser (using the hamburger open in external browser i.e NOT custom tabs, it is able to execute the callback and successfully authenticate.

We do not know if this is actually a Auth0 bug, but as all major browsers works, it may be a particular browser custom tabs issue.

Describe the ideal solution

As using the browser view allows the user to successfully authenticate, we propose that there could be a option which allows us to define a set of browser packages to NOT open the auth url in custom tabs.

e.g in BrowserPicker where you can define a list of disabledCustomTab packages. Much like where you are able to define allowedPackages using withAllowedPackages

Alternatives and current workarounds

Asking the user to change browsers isn't a ideal solution nor something we can control. Especially where users are not always highly tech literate.

Additional context

Vivo_Signin_Unsuccessful.webm

OpenExternal_Vivo_Signin_Successful.webm

[pmathew92]

Hi @bennycao , Thanks for reporting this . I will check to see if this is something we plan to add as a feature or a fix to your issue.
Also would it be possible to share the scheme and Custom tab options you are using while making the authentication request
Thanks

[bennycao]

Hi @bennycao , Thanks for reporting this . I will check to see if this is something we plan to add as a feature or a fix to your issue. Also would it be possible to share the scheme and Custom tab options you are using while making the authentication request Thanks

Hi @pmathew92 , we are using a custom scheme android. I am going to test with https scheme, there were issues raised #656 with issues on samsung android 10, 11 phones with https scheme.
There are other apps in play store who have the same issues with the vivo browser.

Our custom tab option just sets the toolbar color

CustomTabsOptions
            .newBuilder()
            .withToolbarColor(
                contextResolvers.colorResFromAttr(activity, R.attr.Braid_color_surface_brand)
            ).build()

[bennycao]

Created a PR which may be an option for solving for this feature #806

[pmathew92]

Closing this as the corresponding PR has been merged