Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

App Store upload rejected by push entitlements problem

I had to make some changes in my old iPhone app in XCode.

When uploading it to the App Store I get the following problem:

"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."

I have done it that it said. I regenerated all my certificates and so on, but it does not fix my issue.

When I click Fix issue, it comes again and again. enter image description here

Anyway, I had it in my entitlements file (it does not help even if I update it to production)

My certs are ok:

What should I do?

Thanks a lot!

like image 712
Tom Avatar asked Jun 13 '19 10:06

Tom


People also ask

How do I request entitlement from Apple?

Go to https://developer.apple.com/system-extensions/ and click the link to request an entitlement. Apply for the DriverKit entitlement and specify the entitlements you need. Provide a description of the apps you'll use to support your hardware.

What is entitlement file in iOS?

Entitlements are special app capabilities and security permissions granted to applications that are correctly configured to use them. In iOS, apps run in a sandbox, which provides a set of rules that limit access between the application and certain system resources or user data.


2 Answers

Finally, I could solve it:

I deleted all settings from Target / Build settings / Signing in XCode. I don't know exactly why it helped, probably it contained some settings from the past (note, it was not changed for years) that lead to this bug.

Although I leave my question here, hopefully it can save others day in the future.

like image 105
Tom Avatar answered Oct 21 '22 23:10

Tom


I got the problem in xcode 11.3, then I fixed by this way:

  1. Check and note your app Capability in Target -> Signing and Capabilities

  2. Find and remove file name .entitlements in xcode bundle

  3. Search and delete the value of "CODE_SIGN_ENTITLEMENTS" in target -> build settings -> search "CODE_SIGN_ENTITLEMENTS"

enter image description here 4. Add your app Capability again in Target -> Signing and Capabilities -> All

like image 43
QuangLoc Avatar answered Oct 21 '22 22:10

QuangLoc