After changing our app (AppID 779114) from PG 3.4.0 to PG 3.5.0 we received the following warning from iTunesConnect:
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.
Our app does not contain any logic at all for push notifications.
After reverting back to PGB 3.4 and uploading that binary to itunesconnect no warning of that sort was given.
Any clues?
Henk Kelder
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.
Our app does not contain any logic at all for push notifications.
After reverting back to PGB 3.4 and uploading that binary to itunesconnect no warning of that sort was given.
Any clues?
Henk Kelder
- 46 Posts
- 5 Reply Likes
Posted 6 years ago
- 1 Post
- 0 Reply Likes
I have received the message from Apple. Have you had any luck solving it?
- 46 Posts
- 5 Reply Likes
- 8261 Posts
- 263 Reply Likes
Did the following solution helps?
https://www.parse.com/questions/missing-push-notification-entitlement
http://stackoverflow.com/a/22597957
https://www.parse.com/questions/missing-push-notification-entitlement
http://stackoverflow.com/a/22597957
- 46 Posts
- 5 Reply Likes
@Amir:
The problem does *NOT* occur with PGB 3.4
So if there was something wrong with the prov profile or app config it would also occur with PGB 3.4 which it doesn't. It only appears when using PGB 3.5
The first links suggests that the provisioning profile was created before the APP ID was configured to use push. In our app this is not the case. Push was never included in either the APP ID or Prov Profile.
The second link is about trying to add push to an app for which the prov profile is based on on APP ID definition without the pushnotifications. Again, not applicable since our app does not use push at all.
</>
The problem does *NOT* occur with PGB 3.4
So if there was something wrong with the prov profile or app config it would also occur with PGB 3.4 which it doesn't. It only appears when using PGB 3.5
The first links suggests that the provisioning profile was created before the APP ID was configured to use push. In our app this is not the case. Push was never included in either the APP ID or Prov Profile.
The second link is about trying to add push to an app for which the prov profile is based on on APP ID definition without the pushnotifications. Again, not applicable since our app does not use push at all.
</>
- 46 Posts
- 5 Reply Likes
@Amir: I still believe there is something in the PGB 3.5 environment that triggers this error.
- 46 Posts
- 5 Reply Likes
See this thread:
https://groups.google.com/forum/#!sea...
this suggests that the problem is introduced with PG 3.5
https://groups.google.com/forum/#!sea...
this suggests that the problem is introduced with PG 3.5
- 30 Posts
- 0 Reply Likes
This is definitely a 3.5 problem. My last few builds have been with 3.3 and it was okay. I just did a new build where a "recommendation" to use 3.5 came up - it looks like the recommendation ha been automatically applied although I did not okay it - and now I have received this warning message from iTunes.
I think it is just a warning, although we shall see if it gets past the review process. But maybe PG need to look at this?
I think it is just a warning, although we shall see if it gets past the review process. But maybe PG need to look at this?
- 52 Posts
- 0 Reply Likes
I am also having this issue and although Apple is still approving these apps I imagine this will become an issue. Is there anyway we can solve/remedy this?
Thanks.
Thanks.
- 30 Posts
- 0 Reply Likes
My app was approved despite the warning, but maybe it still needs to be looked at. I will rebuild with 3.3 next time just to see.
- 52 Posts
- 0 Reply Likes
Right, as I mentioned, Apple is still approving them. However, I would like to suppress this warning as it might evolve into an error down the road (Apple changes policy on the issue).
- 8261 Posts
- 263 Reply Likes
Hey guys
Can you share screenshot of said warning? I would like to file a feature / enhancement request for dev team to work on.
Please attach it here.
Thanks
Can you share screenshot of said warning? I would like to file a feature / enhancement request for dev team to work on.
Please attach it here.
Thanks
- 30 Posts
- 0 Reply Likes
The message came in an email after uploading the binary as follows:
Dear developer,
We have discovered one or more issues with your recent delivery for "{app name}". 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.
If you would like to update your binary for this app, you can redeliver your binary.
Regards,
The App Store team
Dear developer,
We have discovered one or more issues with your recent delivery for "{app name}". 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.
If you would like to update your binary for this app, you can redeliver your binary.
Regards,
The App Store team
- 4 Posts
- 0 Reply Likes
Yesterday I uploaded an App to the AppStore, the upload was succesfully, but I received the same email from Apple and I'm not using Push Notifications at all.
Any one could solve this warning? It appears that the problem is PG 3.5.0
Phonegap guys help please!
Thanks!
Any one could solve this warning? It appears that the problem is PG 3.5.0
Phonegap guys help please!
Thanks!
- 30 Posts
- 0 Reply Likes
It doesn't seem to affect whether or no your app is approved. Mine was approved okay despite the warning. If you go back to an earlier PG (I use 3.3) then you don't get the warning. Maybe that's a solution until this bug is sorted.
- 4 Posts
- 0 Reply Likes
Well, thanks a lot Deep Blue, I will ignore the warning... Wait the bug will be solved soon for PG.
- 196 Posts
- 6 Reply Likes
I've just got the same warning. I'm using PGB 3.5 and the old version of the app was using 3.4. The only things that have changed are some text changes and a new function that doesn't have anything to do with push notifications.
In your iOS dev account you can add it in the iOS App ID Settings. Problem is you then have to add Apple Push Notification service SSL Certificates, another hoop I do not want to jump through (there are enough!).
The email says "Your delivery was successful, but you may wish to correct the following issues in your next delivery:"
So I'll wait and see if this gets approved and provide feedback.
In your iOS dev account you can add it in the iOS App ID Settings. Problem is you then have to add Apple Push Notification service SSL Certificates, another hoop I do not want to jump through (there are enough!).
The email says "Your delivery was successful, but you may wish to correct the following issues in your next delivery:"
So I'll wait and see if this gets approved and provide feedback.
- 16 Posts
- 0 Reply Likes
Any reason why this is marked as solved? Still getting the email warnings:
Dear developer,
We have discovered one or more issues with your recent delivery for "XXX". 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.
Regards,
The App Store team
Dear developer,
We have discovered one or more issues with your recent delivery for "XXX". 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.
Regards,
The App Store team
- 30 Posts
- 0 Reply Likes
- 14 Posts
- 1 Reply Like
Just uploaded today, got same issue with 3.5, I do not use push notifications in my application
Dear developer,
We have discovered one or more issues with your recent delivery for "CareConnect". 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.
Regards,
The App Store team
Dear developer,
We have discovered one or more issues with your recent delivery for "CareConnect". 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.
Regards,
The App Store team
- 30 Posts
- 0 Reply Likes
As long as the delivery went okay, which it seems to have done, they should approve your app assuming the app itself doesn't have any functional or other issues.
Maybe PGB will fix this in 3.6?
Maybe PGB will fix this in 3.6?
- 8 Posts
- 1 Reply Like
How is this in "Solved" state? What is the solution the the problem that Apple sends these warnings?
I have submitted a PG3.5 project and received the exact same warning.
Even if the warning can be ignored (for now?), it does not mean that this issue has been solved.
I have submitted a PG3.5 project and received the exact same warning.
Even if the warning can be ignored (for now?), it does not mean that this issue has been solved.
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers




