Page 1 of 1
Pitfalls with iOS Development
Posted: Mon May 15, 2017 9:32 pm
by DanShafer
If you have successfully deployed an LC app on iOS or you've made a sincere run at it and found LC fell short, I'm anxious to hear about any pitfalls and workarounds, any warnings or issues you ran into. I'm comfortable with the process on Apple's side and I'm about to test the workflow process in LC with a simple test app but as always I'm sure there are snakes out there waiting to bite me as I delve into more complex apps. So any warnings and similar advice would be most welcome!
Re: Pitfalls with iOS Development
Posted: Mon May 15, 2017 9:48 pm
by LiveCode_Panos
Hi Dan,
The first thing that comes to my mind is that on iOS an Internet connection will be blocked by ATS (Application Transport Security) if it is not considered "secure".
This will affect:
- Any put/post/load url
- Browser widget
- iOS native browser
- Playing remote files using the play command/ the native iOS player
- ..
To prevent this, you have to either use a https connection (recommended) or turn off ATS in the standalone settings (not recommended)
Best,
Panos
--
Re: Pitfalls with iOS Development
Posted: Thu May 18, 2017 9:12 pm
by jekyllandhyde
Dan, Panos,
My IOS App uses get http "non-https connection" calls and I do not have ATS disabled. Everything works fine. The caveat is that I believe Apple allows you to call an IP address over http, but not a domain. Not sure for external domains, but my App was just approved for an internal http call: e.g.
http://192.168.1.10