-
Notifications
You must be signed in to change notification settings - Fork 477
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
Getting the Alamofire NSError #59
Comments
I got the exact same problem, also using version 2.1. Is there any update on this? |
I'm not sure why this would be happening... See the two Response serializers below (they both return the Alamofire error immediately if it exists): What kind of error are you expecting to see that is not returned? You might want to inspect the NSHTTPURLResponse ( |
Yeah i have the same problem, it only retrieves the error of "The operation couldn’t be completed. ObjectMapper failed to serialize response". Could it be posible that the callback is retrieving the success or the failure of the objectmapper action By example, at a service is retrieving me 500 status error code but the function keeps going to the success case. Is there any other way to get the status code or the error message? |
After some research it turns out this is a feature of Alamofire. To get the error, you need to call the |
Thank so much, now it works as expected. |
I am having the same issue i could not retrive the status as expected. Alamofire.upload(data!, with: (myrouter) // what can i put here so that i can retrive the status code like 200 or 500 } |
I'm unable to fetch the Alamofire response error when making a request.
The only error I am able to retrieve is the error
The operation couldn’t be completed. ObjectMapper failed to serialize response.
i'm using version: 2.1
The text was updated successfully, but these errors were encountered: