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.

Add better error reporting.

See original GitHub issue

I’m surprised nobody has asked for this.

Common error conditions:

404 / other http errors. Should report the content and the code.
App is offline error.
App transport security error.

Issue Analytics

State:
Created 5 years ago
Reactions:8
Comments:10 (3 by maintainers)

Top GitHub Comments

9reactions

JeremyBradshaw7commented, Jun 14, 2019

onError is fired for me but doesn’t provide any information about the error, so we can recover but not log any reason to help us debug the issue.

4reactions

DylanVanncommented, May 8, 2018

How about we start with finding some way to stringify whatever SDWebImage or Glide fails with and we pass it back as nativeError on onError. That could be a good starting point.

Top Results From Across the Web

Designing Better Error Messages UX

One simple way of doing so is to improve the discovery errors, by never relying on the color of error messages alone.

Display All PHP Errors: Basic & Advanced Usage

The quickest way to display all php errors and warnings is to add these ... The best way to record these error messages...

Better error reporting [#3172747]

Add all the recipients to the error message. This will quickly identify if there are more individuals being emailed that might cause the ......

Error Reporting

Error Reporting counts, analyzes, and aggregates the crashes in your running cloud services. A centralized error management interface displays the results ...

Error Messages: Examples, Best Practices & Common ...

Useful error messages can keep users on your site and increase conversions. See examples and learn the best practices.