CODEWITHSUNDEEP
iosobjective-capple-push-notifications
Jayasabeen Appukuttan
Jayasabeen Appukuttan

Reputation: 1440

aps-environment is always development

I have created the app id with APNS enabled and I configured both development and production certificate

Now when I create entitlements it is always displaying development even If I change the Provisioning profile to iTunes deployment also the entitlements is displayed as development

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>aps-environment</key>
<string>development</string>
</dict>
</plist>

Upvotes: 86

Views: 76075

Answers (3)

pizzamonster
pizzamonster

Reputation: 1266

Xcode 10.2:

If you change your target to “Generic iOS Device” before Archive, it will set the aps-environment variable to production. If you archive with the target set to your device, it will archive with the aps-environment variable set to development.

Upvotes: 17

Shebuka
Shebuka

Reputation: 3228

You can't use a production certificate in debug/development. Even if you do it, then, when you 'Archive', Xcode will automatically set it to production (Apple reference). You can see this when you try to submit your app to iTunes connect for TestFlight/Review or for Adhoc deployment.

Xcode 8: Xcode 8

Xcode 9: Xcode 9

Upvotes: 115

Jacob King
Jacob King

Reputation: 6167

There is a known bug in Xcode whereby manually setting this to 'production' causes Xcode to display an error next to your entitlements config with a 'Fix Issue' button. Clicking this sets it back to 'development' This is not intended functionality. As I said it is a known issue and I believe I filed a radar when I first discovered it.

It has been fixed in Xcode 8.3 beta 2. In the meantime, manually set it to 'production' and then ignore the error Xcode gives you, your project will work just fine.

Upvotes: 14

Related Questions