Stuck on an issue?
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.
fetch("aaa") has incorrect behavior
See original GitHub issueUnable to catch error thrown from fetch with invalid url. Instead I get a message about “unexpected url”.
- Provide a minimal code snippet / rnplay example that reproduces the bug.
try {
fetch("aaa");
} catch (ex) { }
- Provide screenshots where appropriate
- What’s the version of React Native you’re using? 0.24.1
- Does this occur on iOS, Android or both? Android
- Are you using Mac, Linux or Windows? OS X
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:20 (11 by maintainers)
Top Results From Across the Web
Bad Behavior: Drivers Know It's Wrong, But Many Do It Anyway
New research shows crash-involved drivers admit to risky driving behaviors.
Read more >Making Better Unit Tests: part 1, the AAA pattern - Manning
As you may know, this premise is incorrect. A unit in unit testing is a unit of behavior, not a unit of code....
Read more >Dynamically select OAuth Group in AAA - Forums - IBM Support
In the Identity extraction of AAA, I am trying to reuse the same AAA for different OAuth clients. Can I dynamically pick Registered...
Read more >How To Troubleshoot ISE Failed Authentications ...
If the result of the test aaa command is User authentication request was rejected by server, you know that the switch configuration is...
Read more >[Solved] Please explain the following When the function didnt ...
When the function didn't get the arguments, it expects. ... This incorrect behavior is generated because of the following reasons:.
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 Free
Top 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
I think we should always do 2 and sometimes do 1 as well. That is, convert all native failures to promise rejections, but also do extra validation in JS when we think we can provide better error messages closer to the source of the error.
Re-open it, please.