I take that back. If I turn Android builds back on, close Standalone
Settings, and re-open it, the password is gone. So, we can't protect
Android mainstacks?
Android apps can be distributed through private web sites, and without
any encryption they would be easier to hack. I understand that I can set
the password manually, but it's much easier not to worry about it during
development and still be assurred it will be set on a build.
If there's a reason we can't do that, okay. If there isn't a reason,
I'll put in a request for it.
On 4/15/19 1:10 PM, J. Landman Gay via use-livecode wrote:
Is there a reason we can't encrypt the main stack in standalone settings
when building for mobile?
I can set set a password if I uncheck the mobile app options, set the
password, then re-enable mobile builds, and the password remains. I'm
not sure if it is actually used though when building for mobile. Anyone
know?
--
Jacqueline Landman Gay | [email protected]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
