We have created an App ID, distribution certificate and provisioning profile. Push Notifications were not initially enabled.

We now need to implement Push Notifications in the app.

We have enable Push Notifications in the App D, check the provisioning profile, the provisioning profile was invalid, updated it, and downloaded the latest provisioning profile to use it for next time.

We then integrate the APIs for Push Notifications via APNS in our code.

After uploading the app in iTunesConnect, we get the following email from Apple:

Dear developer,

We have discovered one or more issues with your recent delivery for "Swanvi". Your delivery was successful, but you may wish to correct the following issues in your next delivery:

Missing Push Notification Entitlement - Your app appears to include API used 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. See "Provisioning and Development" in the Local and Push Notification Programming Guide for more information. If your app does not use the Apple Push Notification service, no action is required. You may remove the API from future submissions to stop this warning. If you use a third-party framework, you may need to contact the developer for information on removing the API.

After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.

We have re-checked the App ID. Push Notifications are enabled for development and production.

Thanks for your response. I have gone through the reference, but not so fruitful for me, I have done all the stuff as written there. The app is in waiting for review stage, will that app rejected?
– BisJan 15 '15 at 8:03

Well about a year and half ago, this would be reason to reject app. I'm not so sure about now, because I think that a lot of app validation now goes on when you "validate" app in organizer. So if it went through, you may have a chance to get approved, but don't count on it
– YanchiJan 15 '15 at 8:13

Hi. @Bis, I am facing same issue right now. My application status is "waiting for review". Can you please suggest me that what should I do? And moreover I am not using any push notification in my iOs application.
– Vaishali ModiMar 25 '15 at 13:00

6 Answers
6

You need to see 2 things: The provisioning profiles used by your account on Xcode and the ones on developer.apple

Its all about the provisioning profiles.

STEP 1:
Go to https://developer.apple.com/account/ios/certificate/ and see the Active iOS Distribution Provisioning Profiles you need for your app. Then click on it and make sure Enabled Services has Push Notification enabled. If it doesn't then click on edit and enable it by following the steps provided by Apple. If it is enabled then perfect.

STEP 2:
Delete any Invalid Provisioning Profiles you see related to app (just the invalid ones for YOUR app). I'll tell you why in the following steps.

STEP 3:
Go to Xcode -> Preference -> View Details (for your Account) -> [OPTIONAL: To be sure invalid one is gone, rt-click on any provisioning profile, select "Show in Finder", then Delete/Move all the provisioning profiles from that folder.] Now click Download All Profiles. This will replace local provisioning profiles with current ones. Click DONE.

STEP 4:
Go to your app Targets -> Build Settings -> In Code Signing, expand your Provisioning Profile to show Debug and Release tabs. By default it will be on Automatic (which is why your app was probably automatically using the invalid profile that we just deleted in step 2). For Release, to be on a safer side, select the Active Provisioning Profile with enabled Push Notifications as seen on step 1.

How do I know which one is invalid? I see multiple profiles like "XC *", "XC Adhoc", "iOS Team ..." etc.
– burakcalikMay 25 '16 at 23:06

@burakcalik XC profiles are the one created by XCode by default. You should use the one you want, in most cases it is the provisioning profile you create yourself using the correct app certificate. For me, "XC *" and "XC Adhoc" were either invalid or not the right provisioning profiles, so I deleted them. You can do the same...in no case would anything break, so don't worry. XCode will generate a new provisioning profile if needed.
– Anish KumarJun 1 '16 at 15:25

I did this steps, and the warning comes anyway...
– otmezgerOct 19 '16 at 17:03

@Djeeraj V.S. is correct. Cordova added some conditional compilation to remove this requirement for apps that do not need Push notifications.

You could comment out the code in in Classes\AppDelegate.h as per this answer, but its better to add the compilation symbol DISABLE_PUSH_NOTIFICATIONS via the UI so you can continue to benefit from future Cordova upgrades.

I come from .NET background so i am familiar with conditional compilation but had to spend a bit of time working out how to get the compiler flag working in XCode.

Turns out the magic word here is 'Preprocessor Macro'. Here is how its done graphically via the UI (note that this the way its done in XCode 6.1):

The OP is trying to add Push Notification capabilities to a app that formerly did not support Push. This answer seems to be about removing Push capabilities that were mistakenly added.
– pkambAug 13 '15 at 19:39

Unclear why this answer is on this question - it definitely is NOT an answer to the question "We have enable Push Notifications in the App ID .. email about missing ...". Needs an explanation as to what it is an answer to, and why it is here. (Could stackoverflow have somehow glitched?)
– ToolmakerSteveFeb 14 '17 at 18:17

First of all, when you archive your project, under entitlements if you don't see aps-environment and your app uses push notifications, then you will get the warning mentioned in the question.

FIX STEPS

1- Make sure your distribution profile is valid in Apple's Portal.
- If it's not, then regenerate it.
2- If your distribution profile is valid, then in XCode, navigate to Preferences and then click View Details. At this point under Provisioning Profiles, make sure you don't have invalid distribution provisioning files. If there are invalid ones, then make right click and move them to trash. If you don't have the valid one, then download it from the Portal.
3- Go to Build Settings -> Code Signing and for everything choose the distribution provisioning profile.

At this point if you archive, you can see aps-environment in your entitlements and the warning email won't come.

I have a cordova app, where I have had notifications previously, but wanted to remove it from the app. I tried following the above answers, but I still encountered this issue when I uploaded the build. I realized, that I had a plugin installed, who used the notification setting, and somehow kept some settings activated for notifications.

I solved the issue by removing the ios platform completely cordova platform rm ios, adding it again cordova platform add ios and making sure that the plugin was removed from the ios.json and fetch.json files.