iOS Entitlements not set after update to RC5 [Bug]

Hey guys,

small explanation.
Before I want to upload something to Apples App Store I do this steps.

  1. Git clone repository
  2. npm install
  3. ionic resources ios
  4. ionic platform add ios
  5. ionic build ios --prod

So that nothing can go wrong and everything works fine.
Sometimes a npm -g outdated and then updating the outdated packages.

The last time I did this successfully was on 9th January.

After opening the project in XCode everything looks great.
At capabilities tab I saw Push Notifications checked, Maps checked, Background modes (remote Notifications) checked and Associated Domains checked.

Then now I did the same and only the maps and Background modes tab is checked.
Not the Push Notifications and not the associated Domains.

I found out that the plugins which I’m using (onesignal-cordova-plugin & ionic-plugin-deeplinks) write to the Entitlements file.
I can find them in platforms/ios/MyApp/Entitlements-Release.plist and Entitlements-Debug.plist.

But its not enabled anymore.
I uploaded the file to iTunes Connect and I got a mail that Missing Push Notification Entitlement … the app signature’s entitlements do not include the “aps-environment” entitlement.

I found out that I can solve this by using the –entitlements flag (

Can someone explain me why this changed and why this is not checked automatically?

Its important to know why this things changed without any information so that we can handle things like this in advance :slight_smile:

Thank you really really much in Advance! For any ideas!

1 Like

Ah ok if I use xcodebuild manually I must add the option CODE_SIGN_ENTITLEMENTS = “$(PROJECT_DIR)/$(PROJECT_NAME)/Entitlements-$(CONFIGURATION).plist”.

Then it works :sweat_smile:


Can you be a bit more specific in your solution?

I’m running into the exact same problem when I combine deeplink with onesignal.

I see three entitlements files in my Resources directory–one simply “appName-entitlements”, one “Entitlements.debug.plist” and “Entitlements.release.plist”.

The xcode gui under Build Settings indicates my project is pointing to “Appname.entitlements”

I’ve seen other people say that no matter what they do they can’t get the entitlement to stay as ‘production’ when they upload a build. Can you be a bit more explicit?


@patrick.bussmann Can you please brief this out, I am trying to run a script which generate a ipa which includes all the required capabilities enabled like iCloud for example, able to generate ipa but not able to attach capabilities to the application. your inputs will save my day :slight_smile:

Hi, which cmd you used with –entitlements flag ?