Service invocation fails from android default browser

[Miguel Angel Camacho]

Hi I'm Version 4.1.2
(sorry I've just logged in to the forum with my personal user instead of with my company user Evolucion IP).

Thanks for your help,

Miguel

[Evgene Karachevtsev]

Hello Miguel,

Could you please give us more information? Have you tried to call external service or Appery.io backend service?

[Miguel Angel Camacho]

It's an external service. It works both wehn it's launched from the Appery Test application and from IOS. On Android It is executed only once. The service retrieves a list of items. The first time I request the list it's executed. Then I click on one of the items to see more details and I access the details page for that item.

If I click on the Back button I access to the previous page and I relaunch the service to get the updated list again. I can see debugging the code service.execute is been executed but on the server I can't see any queries. anymore. It only happens in Android.

Any ideas?

[Edwin Schravesande6028557]

I was sort of laying low on this subject, but actually, when testing my app with a large group with different kinds of devices, I still get so many cross browser issues it's hard for me to all single them out.

I got problems on Android-phone default browsers, IE laptop browsers, Ipads... I can't really say my problems are all limited to CORS services. You would of course want to know the specific details, so you can solve them, but that's not that easy when you work with a group of end-users.

It would be a step forward for appery if we could find a way to carefully document crossbrowser incompatibilities. Which will allways be there to some extend, I know... But you can't just demand every end-user to always have the most up-to-date browsers installed.

The best way would be to make a test app, that runs elementary tests that are somehow critical in particular browsers. I could help by running through these tests with a bunch of students every now and then. I guess my students are a pretty representative testinggroup in terms of available devices.

You could even make a plugin that warns users to update once you detect that vital functions will not work in the currently used browser.

Accessibility is key, though I agree there's not much fun in chasing these problems.

[Evolucion Ip]

Hi, is there anything I can do to solve this problem?

Thanks,

Miguel

[Evolucion Ip]

I'm still having the same issue with the service not working in Android devices. Any ideas on how to solve this or what to try to fix it?

Thanks Miguel

[Evolucion Ip]

I've uploaded the following image with the error I'm getting on the Chrome console. Despite of this error the service works fine when testing on the Appery test facility, end on Android, but fails to work on IOs devices.

https://d2r1vs3d9006ap.cloudfront.net...

Can anybody please helo?

[Alena Prykhodko]

Hello,

We'll look into this but it may take some time. Could you please post the screen shot once again? Previous is not readable.

[Miguel Angel Camacho]

Here you are the screenshot again.

[Evgene Karachevtsev]

Hello,

For external services you need to use Appery.io proxy when you test your application on desktop: http://devcenter.appery.io/documentat...
http://devcenter.appery.io/documentat...