The operation couldn’t be completed. (org.openid.appauth.general error -3.)
See original GitHub issueIssue
I have not reproduced the issue on dev/qa environments. Everything that I know from end-user report, app runs webflow and fails immediately after the successful login on the server that
Error The operation couldn’t be completed. (org.openid.appauth.general error -3.)
node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:104:6
node_modules/react-native-app-auth/index.js:187:9
App/Login.tsx:76:42
node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:45:44 tryCatch
node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:271:30
node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:45:44 tryCatch
node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:135:28 invoke
node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:145:19
node_modules/promise/setimmediate/core.js:37:14 tryCallOne
node_modules/promise/setimmediate/core.js:123:25
node_modules/react-native/Libraries/Core/Timers/JSTimers.js:135:6 _callTimer
node_modules/react-native/Libraries/Core/Timers/JSTimers.js:183:17 _callImmediatesPass
node_modules/react-native/Libraries/Core/Timers/JSTimers.js:446:11 callImmediates
[native code] callImmediates
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:396:11 value
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:144:11
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:373:8 value
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:143:17 value
[native code] value
[native code] value
where App/Login.tsx:76:42
is
const loginResult = await authorize(cfg)
Looks like duplicate to https://github.com/FormidableLabs/react-native-app-auth/issues/388
Those errors started after RN upgrade to 0.62.1
. Before that app used 0.59.x
and no bugsnag reports are detected
Environment
- Your Identity Provider: Custom InHouse OAuth Provider powered by Doorkeeper (https://github.com/doorkeeper-gem/doorkeeper)
- Platform that you’re experiencing the issue on: iOS (I have not tried on Android)
- Are you using Expo?: No
"react-native": "0.62.1",
"react-native-app-auth": "5.1.2",
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Org.openid.appauth.general error -6, what is this? - Questions
Hi all, I integrating Okta auth in my iOS app, but I catching this error: error: "Authorization Error: The operation couldn't be completed....
Read more >Google Sign in fails on iOS 13 GM - Stack Overflow
GIDSignIn Code=-1 "The operation couldn't be completed. (org.openid.appauth.general error -3.)" I have no clue how to fix this issue. I' ...
Read more >I'm getting the "Token expired (org.openid.appauth.general error
I'm getting the "Token expired (org.openid.appauth.general error - 15)" error ... This will usually show up if the date and time are set...
Read more >App Auth: error Attempting to load… | Apple Developer Forums
I'm using AppAuth pod to handle user login with Azure in my app. I followed this sample : https://github.com/openid/AppAuth-iOS/tree/master/Examples which ...
Read more >Solved: Log in error On Mobile - Shopify Community
Solved: hello, Can anyone assist me pls. I can't continue to log in as admin to my account (Error: org.openid.appauth.general - 15) 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
Maybe
Error Domain=org.openid.appauth.general Code=-3
meansOIDErrorCodeUserCanceledAuthorizationFlow
and React Native App Auth doesn’t handle user cancellation…I’m a novice in React Native and iOS, I’m just saying…
Creating an delay before calling
authorize
would solve it for me…