`handleAuthorize()` doesent work on targetSdk 30
See original GitHub issueIssue
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
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Permissions updates in Android 11 - Android Developers
Starting in Android 11, whenever your app requests a permission related to location, microphone, or camera, the user-facing permissions dialog contains an ...
Read more >My Android app is not working properly once I set targetSDK ...
So I was updating my app from targeting API 29 to API 30, and some functions broke. How do I figure out the...
Read more >Microsoft identity platform and OAuth 2.0 authorization code flow
The target resource is invalid because it doesn't exist, Azure AD can't find it, or it's not correctly configured. This code indicates the ......
Read more >Error Messages | Maps JavaScript API - Google Developers
Checking Errors in Your Browser; Handling unsupported browsers; If your code still isn't working. This page describes the error messages that can be ......
Read more >Build on Android: Reader SDK - Square Developer
You are using the Android Gradle Plugin version 3.0.0 or later. The Reader SDK might work with 2.3.0 or later, but stability is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In
android/app/build.gradle
addimplementation 'net.openid:appauth:0.8.1'
Also, i changed gradle version in
android/build.gradle
to4.0.1
This worked for me, hope it helps you
~Experiencing a similar issue after updating to React Native 0.65.1 and Android SDK 30. When calling
authorize
fromreact-native-app-auth
(v5.1.1) the following error is returned…~~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…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).