authorize module never resolves after successful login on Android

DigohD commented 2 months ago

Checklist

[X] The issue can be reproduced in the react-native-auth0 sample app (or N/A).
[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description

We've created a barebones React Native project, only implementing the instructions of the quickstart guide in the auth0 dashboard. The login browser module which opens with aurhorize() works as intended, except for when a correct login is entered.

In the Auth0 dashboard logs we can see that registration, email verification and login are successful. But the login module never resolves in the application, and nothing happens after a successful login.

Callback URL configured in the dashboard for the app is: com.authnullte.auth0://digohd.eu.auth0.com/android/com.authnullte/callback

This seems to be correct, since the module does not load at all if we change it.

Reproduction

clone https://github.com/DigohD/auth0-react-native-minimal-repro
install node modules (npm i)
run app on Android device/emulator (npx react-native run-android)
Within the started app, press "Log in"
Register an account via auth0 module and try to log in
if correct credentials are provided, the loading bar of the browser appears and the window is then stuck. Nothing more happens

This is reproducible for all 3 of our develpers who have tried to solve the issue.

Additional context

If we add:

<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
  android:host="digohd.eu.auth0.com"
  android:pathPrefix="/android/${applicationId}/callback"
  android:scheme="${applicationId}.auth0" />

To the AndroidManifest.xml the module resolves after login and we're returned to the application as expected. However, credentials are undefined, either when checking the promise handling argument authorize(...).then(...), or when using getCredentials() provided by useAuth0() hook. We tried both after awaiting authorization and not awaiting.

react-native-auth0 version

3.2.1 and 4.0.0-beta.0

React Native version

0.74.3 and 0.75.3

Expo version

none

Platform

Android

Platform version(s)

14

fabianbru commented 1 month ago

We also experiencing a similar or the same issue with an existing app. There was no change in the code or in the configuration.

During webAuth.authorize the in-app browser opens the login page. After submitting nothing happens and the browser window doesn't close or redirect back to the app. When I manually close the window and try again to webAuth.authorize then the page is empty/white and no login form is visible. This happens till I run webAuth.clearSession (which also stuck with open in-app browser page). Afterwards I see the form again, but it will stuck on submit like at the beginning. There is a "Successful Login" entry in the Auth0 logs.

What I have tried so far, but all result the same:

use Auth0 class or use Provider and Hooks
use up-to-date "react-native-auth0" package and also try 4.0.0-beta.0
use Universal Login or Custom Login page
remove Actions

Due to the fact, that is was functional in the past, it looks like the issue comes from a change made by Auth0 or Android/Chrome?

Does someone have a glue?

fabianbru commented 1 month ago

Found the issue in the code: Our auth0Scheme in build.gradle was missing the .auth0 ending like described in the migration guide

tusharpandey13 commented 1 month ago

Closing this as a root cause and fix has been found.

DigohD commented 1 month ago

Happy to see you got is solved @fabianbru but in our case we have included the ".auth0" part of the scheme and still experience the issue described in the original ticket @tusharpandey13

BrianZanti commented 2 weeks ago

@tusharpandey13 What was the root cause and fix? We are having the same issue described by @DigohD. It doesn't look like there are any newer versions of the sdk which might include a fix.

auth0 / react-native-auth0