Open Category List

What Features Are Lost When An iOS App Is Re-Signed to the Applause Enterprise License?

3 minutesread
  • Home
  • /
  • Knowledgebase
  • /
  • FAQs
  • /
  • What Features Are Lost When An iOS App Is Re-Signed to the Applause Enterprise License?

In addition to Push Notifications€, the following is a comprehensive list of which entitlements/extensions work (and don’€t work) after re-signing to the Applause Enterprise license.More information for developers… iOS-Resigning.

Extension/Entitlement Will Functionality work after resign Comment/Explanation
Access WiFi Information capability NO The Access WiFi Info capability won’t work when signed with Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID must be used.
App Extension YES Resigning removes the specific entitlements keys from both the main app and its extensions (extensions are stored in the app’s Plugins folder). We have implemented an app resigning flow for apps with extensions to use the explicit App ID in order to preserve functionality provided by App Extension capabilities.

To preserve entitlements Applause must use a non-wildcard provisioning profile, which requires that you modify the bundle identifier of the app. For more information, see [Workaround].

App Groups capabilities NO The App Groups capabilities won’t work when signed with the Wildcard profile. Although an option exists to sign using a profile with explicit App ID with App Groups enabled, it is not possible to provide the same group ID as the original app; therefore, the app cannot use this functionality.
Apple Pay capability NO Apple Pay won’t work with the resigned app
Associated Domains capability NO The functionality won’t work because we remove the key to code sign the app
AutoFill Credential Provider capability NO The AutoFill Credential Provider capability won’t work when signed with Wildcard profile. When using the Wildcard profile the key is deleted, which removes the AutoFill Credential Provider functionality. To maintain the functionality the enterprise profile with explicit App ID with AutoFill Credential Provider capability enabled must be used.
Background Modes capability YES Background Modes capability
CarPlay capability NO The CarPlay capability won’t work because we cannot resign an app using the profile containing the original entitlement key. It requires a special entitlement issued by Apple.
ClassKit capability NO The ClassKit capability won’t work when signed with Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with ClassKit capability enabled must be used.
Data Protection capabilities NO The Data Protection capability won’t work when signed with the Wildcard profile. There is an option to sign using a profile with explicit App ID with Data Protection enabled.
Game Center NO Game Center functionality won’t work when signed with the Wildcard profile.
HealthKit capabilities NO The HealthKit won’t work when signed with Wild Card profile. There’s an option to sign with explicit App ID with HealthKit enabled
HomeKit capabilities NO The HomeKit capabilities won’t work when signed with the Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with HomeKit capability enabled must be used. There is an option to sign using a profile with explicit App ID with HomeKit enabled.
Hotspot capability NO The Hotspot capability won’t work when signed with Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with Hotspot capability enabled must be used.
iCloud capability NO The iCloud storage area won’t work between apps since we change the container identifiers
In-App Purchase capability NO The In-App Purchase capability won’t work when signed with the Wildcard profile.
Inter-App Audio capability YES
Keychain Sharing capability NO To resign the app with access groups specified, we replace the access group values with our own team value; therefore, the resigned app cannot access the original access group data as signed by the developer.
Maps capability YES
Multipath capability NO The Multipath capability won’t work when signed with Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with Multipath capability enabled must be used.
MusicKit capability YES
Network Extensions capability YES
NFC Tag Reading capability NO The NFC Tag Reading capability won’t work when signed with Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with NFC Tag Reading capability enabled must be used.
Personal VPN NO The Personal VPN capability won’t work when signed with the Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with Personal VPN capability enabled must be used.
SiriKit capability YES
Wallet (formerly Passbook) capability NO The Wallet (formerly Passbook) capability won’t work when signed with Wildcard profile. To maintain the functionality the enterprise profile with explicit App ID with Wallet capability enabled must be used.
Wireless Accessory Config capabilities NO The Wireless Accessory won’t work when signed with Wild Card profile. There’s an option to sign with explicit App ID with Wireless Accessory enabled.

To learn more about the two types of Apple developers licenses, please go here.

0
0
97
3 minutesread

Related Knowledge Base Posts