New app update: four errors in plist

William de Smet williamdesmet at
Thu Nov 14 13:59:32 EST 2019

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

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 (



More information about the use-livecode mailing list