Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to catch Exception onError method #140

Open
cutiko opened this issue Mar 22, 2016 · 4 comments
Open

How to catch Exception onError method #140

cutiko opened this issue Mar 22, 2016 · 4 comments

Comments

@cutiko
Copy link

cutiko commented Mar 22, 2016

Greetings

We are having problems with the error 0. We cant figure it out what it is. So Im trying to implement New Relic, especifically this:

NewRelic.noticeNetworkFailure(String url, String httpMethod, long startTime, long endTime, Exception e)

This is the New Relic documentation

I have being looking in the repository but cant figure it out, and also trying to cast some of the error.somthing to Exception but is not posible.

How can we catch the exception in the onError method?

[EDITED]
If you are reading this please follow the link to an explanation for the error 0 #139

@orhanobut
Copy link
Owner

Hi @cutiko

I would admit that error handling is poor against the unknown errors. Let me check what I can do with this. Usually when there is an error which is not from network, as default status code is set to 0.

@cutiko
Copy link
Author

cutiko commented Mar 23, 2016

Greetings @orhanobut

Thanks, I hate to ask for so much but we are having a lot of problems with error 0.

#99

#139

Thanks.

@ergunkocak
Copy link

ergunkocak commented Apr 27, 2016

Hi,

Is there a way to catch these exceptions? Like : volley.TimeoutError

@cutiko
Copy link
Author

cutiko commented Apr 27, 2016

@ergunkocak we found a work around, I really like WASP, Im glad I didnt had to change #139 hope to help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants