LiveCode Forums.

I am building an iPad specific app and have a question about loading a separate LC stack file. I prefer to use a LC stack file for storing game related data. LC properties and stack password security make it convenient and easy for all types of complex data formats. However a few years ago Apple was not allowing a LC stack to be loaded by an iOS app from the internet because the file is possibly an executable.

Is this still an issue?

I hope this isn't a duplicate question. I did a search but couldn't find another related topic.

I haven't heard of any LiveCode app being rejected because it uses stack files for a storage format. Apple may require control over the format of prefs files on OS X, maybe also on iOS, but they still allow us to choose our own fomats for other data (and apparently you can still use formats of your own choosing for prefs if you store them outside of the Preferences folder, as all developers who enjoy the freedom of using their own formats have had to do).

The issue with stack files wasn't so much as a data container, but as a container for executable code, and even then the issue wasn't so much with how the app factors code modules on the device as it was to avoid downloading anything that contains executable code not present in the app at the time it was reviewed.

From what I understand of your setup and Apple's requirements, it would seem what you want to do should be fine.

Thanks, that's what I thought, but my memory is getting fuzzy as I enter my 70s. I thought that as long as I used just a regular LC stack file everything was okay. The hidden question, I guess, deals with the ability to include "do" statements as data. Doesn't that provide a way to effectively add executable code to an existing iOS app?

I don't ever want to do that, I just didn't want it to be an issue that would prevent me from loading a LC file.