1
API call works on Android but not iOS
complete
R
Richard Eaton
I’m just completing an App that I’ve been working on and testing throughout on Android and everything works fine. I just went to test my App via the Appgyver App on iOS and an API call (10to8 service) it relies on doesn’t work or appear to return anything. The same identical call is fine on Android.
So 2 questions I guess…
Why would it behave differently on iOS than Android? I thought Appgyver handled all cross platform compatibility.
How can I debug the API calls on iOS to see what is happening?
Thanks!
Richard
Log In
Activity
Newest
Oldest
T
Timo Kapanen
complete
J
Jere Robles
Hi Richard Eaton, I noticed you were able to work this out with Mevi in the forums last October. The issue was a missing forward slash at the end of the URL, that was likely being automatically fixed by internal libraries at the OS level but only in Android.
If it's okay with you I will go ahead and mark this specific report as resolved.
Kind Regards,
Jere
R
Richard Eaton
Jere Robles: thanks anyway!
T
Timo Kapanen
Merged in a post:
API call works on Android but not iOS
R
Richard Eaton
An App I've just completed has an iOS only issue when pulling info from an API (10to8). The App works exactly as expected on Android and other API calls work elsewhere in the App on both iOS and Android ok.
The App ID is 163895 and the issue can clearly be seen on page the "book session" (page ID of 6). A list of available dates/times is shown fine on Android as it should, but is empty on iOS (iPad Mini running iPadOS 14.7). The REST API call is a Get collection (get) on "10to8_booking".
T
Timo Kapanen
under review
T
Timo Kapanen
Hi Richard Eaton, I am going through old tickets and realized this has been left unmanaged for far too long. Apologies for not acting it promptly. Are you still experiencing this issue? We have made quite a few updates since the ticket creation to the platform and also to flow functions. And yes, iOS and Android are expected to work the same way. You can get help for example by using our debugger to see how the content of various flow functions look. Also it is helpful to see if the flow returns error message and what would be the content of the error message. Best Regards, Timo Kapanen
T
Timo Kapanen
Hi Richard Eaton, and sorry for not responding to you earlier. Does the iOS issue still exist in your App? Best Regards, Timo Kapanen
R
Richard Eaton
Timo Kapanen: Hi, yes we're still getting this issue which unfortunately means the App is currently unusable on iOS 😬