Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Better error messges
See original GitHub issueThere are several errors that can occur during the auth flow and although they are passed down to the JS, they could have a better format.
E.g. when the user cancels the popup asking for permission to open the browser and the user cancels, error.message reads as the following:
In this case, the error code is -3, which means either that the user manually canceled the OAuth authorization code flow or the auth request returns with unauthorized_client.
However, it would be very tricky to parse this error properly as it’s in a string and the error.code is just RNAppAuth Error which is not very useful.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we can call this resolved with v6.0.0 where we merged a contribution to expose the OAuth error codes
Ah, fair point. Perhaps I got a bit over enthusiastic with the closing issues 😄
Since this issue was opened, we’ve had two PRs to improve error messages - one was in v5.0.0 to add consistent naming, and the other in v6.0.0 to expose the auth codes. I think it might be best to open a new issue if we need further improvement.
As you’ve just looked into this recently - would you mind explaining what the current error response is, and what you would like to see instead, and we can start a new discussion based on that?