Missing Push Notification Entitlement after building in command line

Question

Created Jan ’21

Replies 2

Boosts 0

Views 3.6k

Participants 2

Firstly, I'm building my app through the command line- unfortunately this is necessary since I'm using Azure DevOps to do the build.

Since the app has an extension I created two provisioning profiles (the app's has Push Notifications capability) and build and sign the ipa via a plist file (multi-provisioning-profiles.plist) as follows:

Code Block xcodebuild -sdk iphoneos -configuration Release -project myapp.xcodeproj -scheme MyApp archive -archivePath myapp.xcarchive CODE_SIGNING_ALLOWED=NO

Code Block xcodebuild -sdk iphoneos -configuration $(Configuration) -project myapp.xcodeproj build -exportArchive -archivePath myapp.xcarchive -exportOptionsPlist multi-provisioning-profiles.plist -exportPath /ipa

The ipa then successfully uploads and a short while later I get the error email (ITMS-90078: Missing Push Notification Entitlement) from Apple regarding push notification entitlements.

Any idea what I might be missing here?

For completeness, here's the multi-provisioning-profiles.plist file also:

<dict>
<key>provisioningProfiles</key>
<dict>
<key>[My app key]</key>
<string>[UUID of app's prov profile]</string>
<key>[My extension key]</key>
<string>[UUID of extension's prov profile]</string>
</dict>
<key>signingCertificate</key>
<string>iOS Distribution</string>
<key>signingStyle</key>
<string>manual</string>
<key>method</key>
<string>app-store</string>
<key>teamID</key>
<string><[My team ID]</string>
</dict>
</plist>

Answered by benjfromlondon in 658472022

The problem seemed to stem from not signing the archive (CODESIGNINGALLOWED=NO is bad in this case). Once the xarchive was signed with the provisioning profiles then I no longer received the email from Apple after uploading.

I'd originally avoided signing the archive because I'd struggled to get it working with more than one provisioning profile but eventually found the following solution: https://stackoverflow.com/a/29605731/2520623

For reference, this is what my final archive command looked like:

Code Block xcodebuild -sdk iphoneos -configuration Release -project myapp.xcodeproj -scheme MyApp archive -archivePath myapp.xcarchive -allowProvisioningUpdates OTHER_CODE_SIGN_FLAGS=--keychain tempkeychain.keychain APP_PROFILE=[UUID of app's prov profile] EXTENSION_PROFILE=[UUID of extension's prov profile]

Boost

Answer 1

benjfromlondon OP

Jan ’21

Accepted Answer

The problem seemed to stem from not signing the archive (CODESIGNINGALLOWED=NO is bad in this case). Once the xarchive was signed with the provisioning profiles then I no longer received the email from Apple after uploading.

I'd originally avoided signing the archive because I'd struggled to get it working with more than one provisioning profile but eventually found the following solution: https://stackoverflow.com/a/29605731/2520623

For reference, this is what my final archive command looked like:

Code Block xcodebuild -sdk iphoneos -configuration Release -project myapp.xcodeproj -scheme MyApp archive -archivePath myapp.xcarchive -allowProvisioningUpdates OTHER_CODE_SIGN_FLAGS=--keychain tempkeychain.keychain APP_PROFILE=[UUID of app's prov profile] EXTENSION_PROFILE=[UUID of extension's prov profile]

1

Answer 2

osmangokc OP

Nov ’21

i have same issue. but in my case there are 1 more prov profile extra. 1 app profile and 2 extension profile. how can i deal with it? may you share your azure pipeline yaml if you do not mind? should i insert xcodebuild command manually to the yaml? or can i use xcode build task from azure devops modules?

0