Alamofire returns different result from what is expected

Question

I am using Alamofire at my app and it returns a different response from what it should return (I've tested with Postman several times).

What I am doing is I simply call a webservice which returns a list of JSON objects. Here is the code if you want to take a look:

Alamofire.request(Constants.ENDPOINT_GET_PROF_CALENDAR, method: .get, parameters: params).responseJSON{
        response in
        if response.result.isSuccess{
            let rawResult = JSON(response.result.value!)
            self.parseResponse(json: rawResult)



        }else{
            print("Error getting appointments")
        }
    }

For example the response is like this:

{"busy": [
    {
        "type": "Busy",
        "date": "2019-08-15",
        "timeslot": "07:00-22:00",
        "address": "No address",
        "id": "41769"
    }, //item 1
    {
        "type": "Busy",
        "date": "2019-08-22",
        "timeslot": "08:00-17:00",
        "address": "αθήνα",
        "id": "41670"
    }, //item 2
    .
    .
    .
}

If I make same request with postman it returns more items(A different response) than in Alamofire. What is going wrong?? It looks like Alamofire returns the same thing again and again. This is really weird to me and I would appreciate it if someone knows what is going on!

Can you print the Alamofire JSON response before parse? The items count is less than Postman? — alxlives, Aug 21 '19 at 20:56
@alxlives No matter what, it looks like Alamofire returns always the same response back. I omitted to copy and paste the response as it will make the post more difficult to be read — Kwnstantinos Nikoloutsos, Aug 21 '19 at 21:00
Try adding this method before loading the data: `URLCache.shared.removeAllCachedResponses()` — alxlives, Aug 21 '19 at 21:05
Same thing... I really don't know what is going wrong. Other calls to webservice seems like working well. I am checking my code again and again.. — Kwnstantinos Nikoloutsos, Aug 21 '19 at 21:10
It looks like a cache issue. Can you try this solution? https://stackoverflow.com/a/46489244/3241041 — alxlives, Aug 21 '19 at 21:14
Hmm i will try to fix it. The only logical reason for this to happen is that the response is cached and reused! Thank you for your help — Kwnstantinos Nikoloutsos, Aug 21 '19 at 21:22
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/198267/discussion-between-kwnstantinos-nikoloutsos-and-alxlives). — Kwnstantinos Nikoloutsos, Aug 21 '19 at 21:47

score 1 · Accepted Answer · answered Aug 21 '19 at 22:04

It seems it was really a cache issue. Following this solution, we could do something like this:

 var req = URLRequest(url: URL(string: Constants.ENDPOINT_GET_PROF_CALENDAR)!)
 req.httpMethod = "GET"
 req.setValue("application/json", forHTTPHeaderField: "Content-Type")
 req.cachePolicy = NSURLRequest.CachePolicy.reloadIgnoringCacheData

 Alamofire.request(req).validate().responseJSON { response in
        if response.result.isSuccess {
            let rawResult = JSON(response.result.value!)
            self.parseResponse(json: rawResult)
        }else{
            print("Error getting appointments")
        }
    }

Alamofire returns different result from what is expected

1 Answers1