Prevent Duplicate "Open With" Modal When Authenticating via Google Sign-In

[orel-asper]

Checklist

• The issue can be reproduced in the react-native-auth0 sample app (or N/A).
• 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.

Description

We observe an unexpected behavior upon authenticating through Google sign-in. Upon completing the sign-in process successfully, the system presents the user with an "Open With" modal featuring our app twice. How do we eliminate the redundancy and display only a single instance? Thank you!

React Native version 0.63.5
react-native-auth0: 2.11.0-2.15.0

happens on Android 14

Reproduction

In order to reproduce the issue, here are the steps to follow:

Begin navigating inside the application, triggering the need to authenticate the user.
Attempt to authenticate using the webAuth.authorize(...) method along with valid credentials.
At this point, the user will be redirected to Chrome for initiating the authentication process.
Following a successful authentication attempt, the user encounters an "Open With" dialog box listing the application twice.
A screenshot has been included in the GitHub repository showcasing this problem: <https://github.com/auth0/react-native-auth0/assets/67417080/d2b2f421-9167-428c-a688-c89cad691c55>

The main concern lies in preventing the appearance of the duplicated "Open With" modal, restricting it to just a single occurrence. Thanks for considering this issue!

Additional context

No response

react-native-auth0 version

2.11.0

React Native version

0.63.5

Expo version

No response

Platform

Android

Platform version(s)

14

[bijudhungel1177]

@orel-asper did you find any solution ?

[poovamraj]

@orel-asper @bijudhungel1177 This issue occurred in the older version of our SDK using Expo where the intent that was used was same as one used by Expo. You can see our migration guide to v3 explaining how this can be fixed - https://github.com/auth0/react-native-auth0/blob/master/MIGRATION_GUIDE.md#upgrading-from-v2---v3

Can you try this and let us know your feedback?