I have a cordova application that runs fine on old iOS versions and on Android devices as well. With the release of iOS 10 it started throwing timeout error if the AJAX request took more than a minute to return data. Please help me with this issue at high priority
AJAX issue with iOS 10
Any news on this? I have a Cordova APP ready to launch (my bosses even organized a event later this month) but it is not working due to this issue.
This has been fixed in WebKit: https://bugs.webkit.org/show_bug.cgi?id=163814
Once Apple releases an iOS update with the included WebKit updates, we'll be set.
Have you checked preflight configuration in your server ? I faced same issue. I handled preflight request in my server that solved the issue. 🙂
Anyone know where to look for a target iOS release for this? It looks like that WebKit fix was closed on 10/29. I am running 10.2 Beta 2 which came out afterward, and I still have the issue.
It's allegedly fixed in iOS 10 beta 3 (haven't tried it yet myself) so we should be all set when it hits the masses in December.
No such luck. As soon as Beta 3 came to my iPhone, it didn't get any better. We actually override the timeout in the Ajax request to 5min for some processes, no matter what it is set to, right after 60 seconds the request fails. I tried this inside my app as well as through safari and the result was the same. Apple...please let us know when this will be fixed and on what Release!
Still same status here. Just tested iOs 10.2 Beta 5, overriding the timeout in an ajax request (setting it to 3 minutes).
Sadly enough, the request will terminate after 60 seconds..
Just downloaded BETA 6, still same status - timeout after 60 secounds.
Hi,
Is there any luck with this issue? This thread https://issues.apache.org/jira/browse/CB-11906 says that the issue is fixed but looks like it is not.
Regards
This seems to be a iOS/Safari level bug as it is happening with non-Cordova applications as well. We are facing this issue only on iOS devices and not on mac.
I just tested on iOS 10.2, but the error remains. Can anyone else confirm, that the error is resolved with 10.2?
No, this has not been resolved yet. 10.2.1 Beta1 has been tested and confirmed as issue still existing. Hopefully soon. This issue lies in WebKit.
Try on latest iOS 10.2.1 Beta 2. This looks like fixed in this release.
raghava is correct. Give your apps a try now with 10.2.1 Beta 2 (14D15). My recommendation is for developers to become familiar with WebKit and leverage its nightly builds to test your applications if at all possible so you are not caught off guard on new updates that integrate this (iOS, macOS, Chrome, etc.)
For reference. https://trac.webkit.org/changeset/209776