404 ios error

[meandmymonkey7]

I have searched and made sure there are no existing issues for the issue I am filing

• I have searched the existing issues

Description

This is a very weird issue affecting only a few ios users so I really can't give you much details. I only know it is happening at ios devices (with different models or os versions) and it has been happening even when sdks where released by appcelerator team. So this is not a recent change.

Whenever we try to make a rest api call to our server we get a 404 Not found error.

I know you will say this seems a server side issue but the weird thing is that the issue gets resolved if app is deleted and reinstalled!

At some cases users never have the issue again, at others they have to install app every day.

Expected Behavior

Successful rest api calls.

Actual behavior

404 error on rest api calls

Reproducible sample

Random received from very few ios users as feedback

Steps to reproduce

Install app, try to perform a rest api call if this happens you get 404 as response.

Platform

No response

SDK version you are using

11.1.1.GA

Alloy version you are using

No response

[m1ga]

did you try to call a different server e.g. http://httpbin.org/post and check that output (http://httpbin.org/#/HTTP_Methods/post_post). Or check Android with your server and check if there are 404 errors.

From my standpoint its very hard to tell without any code. I use httpclient calls without issues on iOS and Android.

[meandmymonkey7]

I know this is hard to catch. Everything works well on our end as well so I can't perform such tests. To give you some numbers we have let's say about 24k active users. 16k using Ios and 8k using Android. We have never heared this from an Android user so there is certainly no issue there. Out of the 16k ios users we have heared this from no more than 100 people. (at a timeline of a couple of years) It is proven that deleting app resolves the issue, it has worked for everyone even if this might be temporary so my guess is that something is stored somewhere at app cache by ios causing this. This could be ios related only and not titanium. Just trying to figure this out as well.

[meandmymonkey7]

Just thinking out loud, is there some way we could clear http client cache from titanium? I think this could resolve the issue and we could apply this on a daily basis for ios if it could be possible.

[m1ga]

But that would imply, that the API url changed and the cached endpoint will bring a 404? The easiest way to ignore the cache is to add random parameters at the end of the URL. I use this for profile images when you change them. Sometimes the user got the previous image after going back to the homescreen. Adding a random number will always request a new URL.
But in my case its the same URL and it will just reply with old content. For iOS you can set the cache property but it should be false by default. Or try something like https://stackoverflow.com/a/14832400/5193915 with hyperloop or a module. I'm not an iOS dev so I can't help you with code

[meandmymonkey7]

The url is the same. What changes from one day to the other is the header. We have a token that is renewed daily and we send this as a header so maybe this causes the issue. We will try the suggestions and see how it goes, thank you very much for your help.

[hansemannn]

Hey there! I definitely need some reproducible test case here to proceed. Please check if the URL may be encoded on one platform or the other - I noticed cases where that can make trouble.

[hansemannn]

Any update here? Happy to fix it if we have a sample case :)