Handling Errors with responseDecodable about networkingexample HOT 6 OPEN

Someone on Stack Overflow pointed me in the right direction with this. Obvious really, now I think about it.
Alamofire will return a failure response because it could not decode the body of the response (not because it was a failure HTTP status code). Therefore we need to also chain the .responseDecodable to .validate(statusCode: 200..<300).

That way, when we get a failure code returned by our server, we can check response.result.isSuccess using a guard statement and if there is a failure, we can handle it from there. My requirement is that the error is decoded, if possible, into a particular error struct I created - so I do that in another method and it is returned as an optional as part of the completion handler. Again to reiterate, with my requirement it may not be possible to decode that error - so I have a generic error response to handle that.

Still need to do some more testing, but it seems to work fairly well for my needs.

I think that handling errors could be explained a little bit in this article. Don't get me wrong, it's a very descriptive and well thought out article, but I think it's important to talk about errors too.

from networkingexample.

Assume server responds with 200 status code and send some generic error in the response, but Alamofire tries to decode the mentioned object which will fail inevitably so how can we handle this situation?

from networkingexample.

+1 @beninabox 's comment. If a 401 error is returned this isn't going to be handled by the example code.

from networkingexample.

@beninabox same problem with me, how can you solve it, thanks ?

from networkingexample.

Someone on Stack Overflow pointed me in the right direction with this. Obvious really, now I think about it.
Alamofire will return a failure response because it could not decode the body of the response (not because it was a failure HTTP status code). Therefore we need to also chain the .responseDecodable to .validate(statusCode: 200..<300).

That way, when we get a failure code returned by our server, we can check response.result.isSuccess using a guard statement and if there is a failure, we can handle it from there. My requirement is that the error is decoded, if possible, into a particular error struct I created - so I do that in another method and it is returned as an optional as part of the completion handler. Again to reiterate, with my requirement it may not be possible to decode that error - so I have a generic error response to handle that.

Still need to do some more testing, but it seems to work fairly well for my needs.

I think that handling errors could be explained a little bit in this article. Don't get me wrong, it's a very descriptive and well thought out article, but I think it's important to talk about errors too.

Can you share an example?

from networkingexample.

Just update
request.responseDecodable(decoder: decoder, completionHandler: { (response: AFDataResponse) in
to
request.responseDecodable(decoder: decoder, completionHandler: { (response: DataResponse) in

from networkingexample.