Build warning : Missing Push Notification Entitlement

[Alon_I_]

How do i remove this warning when i build my cordova project to ios ?

I am not using any plugin with notifications on the xdk project (none of the plugins or 3rd party plugins is checked)

Otherwise all is working fine but i would like to get rid of this before trouble will come later from apple.

This is what i get after uploading ipa with application loader 

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.

[John_H_Intel2]

Are you using any 3rd party plugins that did not come from the XDK?

When you created your provisioning profile on apples site, did you enable push notifications for the provisioning profile.

[Alon_I_]

Hello John

I chekced ...My provisioning profiles include only : Game Center, In-App Purchase

as for the plugins i use construct 2 plugins and a 2 additional plugins (iap and statusbar) tht were made by a  3rd party developer both are not related to push notifcations in anyway.

Alon

[John_H_Intel2]

What is giving you this message? 

Missing Push Notification Entitlement

[Alon_I_]

i dont know. all i know is that i build the app via xdk upload via application loader and then get this warning from itunes connect after the build was uploaded

[Alon_I_]

John Hi,

I removed the third party plugin , only using construct 2 clean. still problem exists i guess this is related to intel xdk adding push notification code unintentionally. I guess it is a bug

[John_H_Intel2]

I just built a construct 2 app and uploaded it and did not get the message you are indicating your got. My project had 0 plugins included.

[John_H_Intel2]

Ok, I see the issue now. Its an EMAIL that Apple sends you AFTER you successfully submit through Application Loader. In the future, please be very specific about things like this so we can assist you more efficiently. I am going to rebuild, not a construct 2 app and see what happens. If I dont get it, then its a construct 2 problem.

[John_H_Intel2]

Ok, I found the culprit. It is an underlying issue with Cordova. The push code is included by Cordova be default with 4.1.2. I rebuilt with 3.5 got the email. AFAIK apple will not reject your app for this.

[Alon_I_]

Hi John,

sorry about the confusion - i did mention on my post that i get the warning after uploading the ipa via application loader on the first post. but maybe i wasnt clear enough

so compling with cordova 3.5 will solve the issue ? Arent there any disatvatages of using an older version of crdova (copatipibility / performance etc?)

Thanks for your help!

Alon

[John_H_Intel2]

No, Cordova 3.5 will not fix the issue either. Its a Cordova issue, not an XDK issue. Google it and you will see others complain about the same issue.

[Alon_I_]

Gotcha,

well i thought that untel could dig into that open source and fix it :) or at least add on/off checkmark inside of the xdk.

Alon 

[John_H_Intel2]

We could technically, but then we would be in the business of maintaining our own branch of Cordova, which is not something that we plan on doing. Instead, the fix should come from Cordova, so get on them to fix it :)

[Alon_I_]

tell me who to nudge there and trust me i'll do it :)

[PaulF_IntelCorp]

We will be offering a CLI 5.x builder in a future release. That should resolve the problem, if it has been fixed in the iOS Cordova framework.