New app update: four errors in plist

J. Landman Gay jacque at
Thu Nov 14 20:06:52 EST 2019

Is the location key included in the plist if you don't select location 
services in standalone settings? (I haven't built for iOS in a long time.)

Jacqueline Landman Gay | jacque at
HyperActive Software |
On November 14, 2019 3:05:17 PM Ralph DiMola via use-livecode 
<use-livecode at> wrote:

> ITMS-90339: from iOS 12(or 13?) an app automatically does NOT exit on
> suspend. You need this key for legacy OS versions. You will not be rejected
> for this(yet).
> ITMS-90078: will also not get you rejected. This is caused by some library
> binding issue that Mark explained a while back.
> ITMS-90191: Also a warning. This is for Beta testing. You can enable the
> beta entitlement when generating a provisioning profile.
> ITMS-90683: This is the one that will get you rejected. For example if you
> use location services you will have to hack the IDE to change the text of
> the location request text. This can be a pain because you have to do it
> every time the IDE is started. What I do:
> 1) In the message box ==> "put the script of "revSaveAsIosStandalone" into
> url ("File://somePath/someFilename")
> 2) Edit the text file(See QCC 22150)
> After that every time you want to submit to the app store do this in the
> message box ==> set the script of "revSaveAsIosStandalone" to url
> ("File://somePath/someFilename")
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdimola at
> -----Original Message-----
> From: use-livecode [mailto:use-livecode-bounces at] On Behalf
> Of William de Smet via use-livecode
> Sent: Thursday, November 14, 2019 2:00 PM
> To: How to use LiveCode
> Cc: William de Smet
> Subject: New app update: four errors in plist
> Hi there,
> Today I uploaded an update for one of my apps to the App Store.
> Now I have four errors coming back from Apple.
> Still need to edit the info.plist but it'd easy to make a mistake with this.
> When will this be fixed?
> -----
> Got this notification back:
> ITMS-90339: Deprecated Info.plist Key - The Info.plist contains a key
> 'UIApplicationExitsOnSuspend' in bundle shutthebox [] that
> will soon be unsupported. Remove the key, rebuild your app and resubmit.
> ITMS-90078: Missing Push Notification Entitlement - Your app appears to
> register with the Apple Push Notification service, but the app signature's
> entitlements do not include the "aps-environment" entitlement. If your app
> uses the Apple Push Notification service, make sure your App ID is enabled
> for Push Notification in the Provisioning Portal, and resubmit after signing
> your app with a Distribution provisioning profile that includes the
> "aps-environment" entitlement. Xcode does not automatically copy the
> aps-environment entitlement from provisioning profiles at build time. This
> behavior is intentional. To use this entitlement, either enable Push
> Notifications in the project editor's Capabilities pane, or manually add the
> entitlement to your entitlements file. For more information, see
> /Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_r
> ef/doc/uid/TP40008194-CH6-SW1
> .
> ITMS-90191: Missing beta entitlement - Your app does not include the
> beta-reports-active entitlement. If you intend to distribute this build via
> TestFlight for beta testing, please re-build this app with an App Store
> Distribution provisioning profile. Do not use ad-hoc profiles.
> ITMS-90683: Missing Purpose String in Info.plist - Your app's code
> references one or more APIs that access sensitive user data. The app's
> Info.plist file should contain a NSLocationAlwaysUsageDescription key with a
> user-facing purpose string explaining clearly and completely why your app
> needs the data. Starting Spring 2019, all apps submitted to the App Store
> that access user data are required to include a purpose string. If you're
> using external libraries or SDKs, they may reference APIs that require a
> purpose string. While your app might not use these APIs, a purpose string is
> still required. You can contact the developer of the library or SDK and
> request they release a version of their code that doesn't contain the APIs.
> Learn more (
> _s_privacy
> ).
> -----
> Greetings,
> William
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:

More information about the use-livecode mailing list