`handleAuthorize()` doesent work on targetSdk 30

[andrejhristovski]

Issue

I needed to upgrade my targetSdk to 30 so i can add the app to google play, but for some reason the authentication stops working, when i call handleAuthorize() it doesn't work , it throws Error: Error not specified.

---

Environment

• Your Identity Provider: IdentityServer 4
• Platform that you're experiencing the issue on: iOS / Android / both
• Are you using Expo? No

[mrbrentkelly]

Experiencing a similar issue after updating to React Native 0.65.1 and Android SDK 30. When calling authorize from react-native-app-auth (v5.1.1) the following error is returned...

{"code": "browser_not_found", "message": "Error not specified.", "nativeStackAndroid": {}, "userInfo": {}}

Going to try updating to the latest version of react-native-app-auth to see if that helps any 👍

Update after upgrading to v6.4.0

So in version 5.1.1 on RN65.1 and Android 30 I would just get an immediate failure when calling authorize(), but version 6.4.0 is slightly better...

I now get redirected to chrome when calling authorize() to an Okta page (we using Amazon Cognito and Okta), I can enter a username and password, but after clicking login on Okta I get redirected back to the app with the following error...

{"code": "token_exchange_failed", "message": "Invalid ID Token", "nativeStackAndroid": {
"0": {"class": "net.openid.appauth.IdToken", "file": "IdToken.java", "lineNumber": 202, "methodName": "validate"}, 
"1": {"class": "net.openid.appauth.AuthorizationService$TokenRequestTask", "file": "AuthorizationService.java", "lineNumber": 698, "methodName": "onPostExecute"}, 
"2": {"class": "net.openid.appauth.AuthorizationService$TokenRequestTask", "file": "AuthorizationService.java", "lineNumber": 564, "methodName": "onPostExecute"}, 
"3": {"class": "android.os.AsyncTask", "file": "AsyncTask.java", "lineNumber": 771, "methodName": "finish"}, 
"4": {"class": "android.os.AsyncTask", "file": "AsyncTask.java", "lineNumber": 199, "methodName": "access$900"}, 
"5": {"class": "android.os.AsyncTask$InternalHandler", "file": "AsyncTask.java", "lineNumber": 788, "methodName": "handleMessage"}, 
"6": {"class": "android.os.Handler", "file": "Handler.java", "lineNumber": 106, "methodName": "dispatchMessage"}, 
"7": {"class": "android.os.Looper", "file": "Looper.java", "lineNumber": 223, "methodName": "loop"},
"8": {"class": "android.app.ActivityThread", "file": "ActivityThread.java", "lineNumber": 7656, "methodName": "main"}, 
"9": {"class": "java.lang.reflect.Method", "file": "Method.java", "lineNumber": -2, "methodName": "invoke"}}, "userInfo": {}},
"10": {"class": "com.android.internal.os.RuntimeInit$MethodAndArgsCaller", "file": "RuntimeInit.java", "lineNumber": 592, "methodName": "run"}, 
"11": {"class": "com.android.internal.os.ZygoteInit", "file": "ZygoteInit.java", "lineNumber": 947, "methodName": "main"}

If I initiate the authorize flow right after then it's successful (because it doesn't need to go through Okta again as its just been authorized).

[verybluebot]

Having the same, I think its same as issue #684

Still need to dig deeper

[AlkanV]

we have the same issue at the moment. After updating to targetSdk: 30, we started to get this error. Below android 11 devices, it is working.

[andrejhristovski]

In android/app/build.gradle add implementation 'net.openid:appauth:0.8.1'

dependencies {
    //noinspection GradleDynamicVersion
    implementation 'com.facebook.react:react-native:+' 
    implementation 'net.openid:appauth:0.8.1' // add this line
    implementation 'androidx.browser:browser:1.2.0'
}

Also, i changed gradle version in android/build.gradle to 4.0.1

buildscript {
 dependencies {
        classpath("com.android.tools.build:gradle:4.0.1")  // modify this line
        classpath ('com.google.gms:google-services:4.3.3')
    }
}

This worked for me, hope it helps you

[hugo-chq]

Getting the same "Invalid ID Token" error on android 31, react-native 0.66.3

the fix didn't seem to work for me, although everything still works on android 29

EDIT:
thanks @andrejhristovski , It's working when making the changes to node_modules (I was previously editing files in src/android),
I changed gradle to 4.0.1, and appauth to 0.10.0, both in node_modules/react-native-app-auth/android/build.gradle

this is the patch used with patch-package ( the changes can be manually made then this patch is generated with npx patch-package react-native-app-auth )

diff --git a/node_modules/react-native-app-auth/android/build.gradle b/node_modules/react-native-app-auth/android/build.gradle
index 85fb638..29b3a76 100644
--- a/node_modules/react-native-app-auth/android/build.gradle
+++ b/node_modules/react-native-app-auth/android/build.gradle
@@ -12,7 +12,7 @@ buildscript {
             google()
         }
         dependencies {
-            classpath 'com.android.tools.build:gradle:3.5.3'
+            classpath 'com.android.tools.build:gradle:4.0.1'
         }
     }
 }
@@ -56,6 +56,6 @@ repositories {
 dependencies {
     //noinspection GradleDynamicVersion
     implementation 'com.facebook.react:react-native:+'  // From node_modules
-    implementation 'net.openid:appauth:0.8.1'
+    implementation 'net.openid:appauth:0.10.0'
     implementation 'androidx.browser:browser:1.2.0'
 }

it also required the AndroidManifest.xml fix from #684 (comment)

EDIT 2:

Sometimes this error comes up again and doesn't go away, and a temporary workaround is to wipe all android simulator data

EDIT 3:
The issue was the emulator time became incorrect, fixing the time removed the issue

[Jay-A-McBee]

I've been running Android 30 as the targetSDK for the example app in the project and testing on the emulator also on Android 30 today. I have not been able to replicate this issue. The Example app required 0 changes. The library has also been on the updated version of AppAuth-Android for the last 8 months (necessary to support Android 30). Closing this out.

[yberstad]

@hugo-chq, thank so much for your suggested fix, worked like a charm for us! We have had more and more of the "browser_not_found" error in production lately.