Forum | Appery.io

Thank you Marco,

The Android 2.3 problem is reported and will be resolved.

Thanks, I appreciate your effort.

This sounds like exactly the kind of problems I'm dealing with. This is like a fifteen percent fail in the university classes I'm teaching in and can be quite a showkiller.

Did someone fix something on this issue? Is there a workaround? A JSONP way?

Would hosting it at an appery domain solve the issue?

Hi Edwin - I will clarify with developers about the workaround, for now the solution is to use user-installable browser that uses their own rendering engines (e.g. Opera, Firefox).

We'll update on Monday when we'll have more information.

Hi Edwin,

This should be helpful:
http://www.kinvey.com/blog/107/how-to...

Thnx! I guess I should get some help and take some time to really take the next step with this, but it looks like a source that really gets into the details of this problem and gets us some solutions.

What I don't really get: if I host my app on {}.app.appery.io, and call to your server, that wouldn't be a cross domain call, would it? But it doesn't work either.

HI Edwin,

Sorry for the disinformation. Our developers are working on a workaround according to the link I posted above. If it is successfully implemented, I'll update.

It would be a cross domain call that will be properly processed on modern browsers. But there are some problems with Android 2.3. We are currently searching for a solution.

Hi Edwin,

Android 2.3 is not supported. Android 2.3 browser does not include the Origin header to CORS GET request and the workaround we tried didn't work.

Hi I'm having a similar problem. I've got a rest service working perfectly on IOs devices, but not on Android. It is configured with proxy on the service settings but still doesn't work. Any ideas of why this could be?

Thanks in advanced,

Miguel

Hi Miguel,

Please clarify what version of Android is on your testing device?