Catch up wih the Appery.io community on our forum. Here you'll find information on the lastest questions and issues Appery.io developers are discussing.
https://forum.appery.io/
When I use the web app inside the default browser on Android (v. 2.3.6), calling a database service fails unless I enable the Appery Proxy for the service.
Same app on the same Android, but different browser (Firefox v. 21.0), everything works well. Any idea?
Thanks
Hello! Please take a look here http://docs.appery.io/documentation/a...
Thanks for the reply. I have already read that documentation.
What I would know is if there is a way to make Appery database services work with default browsers on Android.
Since services are on your server, I cannot apply any cross-domain strategy.
Could you clarify are you running published app in browser or just public app link?
I'm running the app from the public app link.
Hi Marco,
Different browsers have different behaviour on cross-domain requests, especially mobile browsers.
Could you please share your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a or give us a public link?
Do you connect to Appery.io database or somewhere else?
I'm calling a Appery.io database service.
I created this page to check the issue:
http://appery.io/app/view/a1945e03-a0...
The label changes to "Service OK" on service success, to "Service FAIL" on service error.
In the default browser on Android the service works only if I enable the Appery Proxy, otherwise it fails.
Currently I disabled the Proxy so you can reproduce the issue.
Hi Marco,
The problem really exists and we faced it before. You should use another browser or newer version.
OK. It's not a problem to me, I can use a different browser and I actually do.
As you can understand I want to provide the best user experience, and saying to people to change the browser before they can give the application a try is not a great deal.
Anyway, I understand that old browsers are the problem: do you have any workaround to suggest?
Do you think that a DNS mapping of a my subdomain (of the domain where I run the app) to your service domain can solve the problem?
For example, mapping apperyservices.myapp.com to your domain, while running the app from app.myapp.com
Hi Marco,
As for browsers - I would advise to use new ones.
But we'll search for a solution.