LiveCode Forums.

Colleagues

Just uploaded an update to an iOS App for iPad and everything worked without a hitch via Application Loader, version 2.8. However, we received an email from Apple which included the following:

Missing Push Notification Entitlement - Your app appears 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.

None of the application settings were changed in LiveCode - specifically the Push Notification option is not enabled and push notifications are not used by the App. The App ID is not enabled for Push Notifications in the Provisioning Portal either.

The question is, what has changed for this message to be sent after a successful upload? Is this an additional screening process in iTunes or is LiveCode somehow attempting to register for the service regardless of the application setting? Any thoughts or suggestions?

Will provide an update on the outcomes from this submission in due course.

Dave

Hi Dave

I got the same problem. It looks like many got that, see below, but the apps get approved anyhow. So no need to act at all.

I created a new certificate at Provisioning Center which included Push for Production, but that did not help, I got the same email again after new binary was successfully submitted.

It looks like aps-environment entitlement would also have to be submitted but I don't know how or where to do that. (Would you?)
So I quit and let it go as it is and it will be approved anyway.

I also think those emails are produced by a change in how iTunes checks the binary, maybe they correct that on their side and the emails will stop in the future.

Some opinions of other forums:
- I have recreated my Distribution provisioning profile and build my application with it. This change fixed the issue of Missing Push Notification Entitlements.
- I received this same error message, and recreating my provisioning profile didn’t eliminate it.
Instead I found that my app contained some stray APNS-related symbols (in a library) that weren’t being used. Apparently they caused a static analyzer to mark the app as using push notifications (it doesn’t). #ifdef-ing out the symbols allowed my app to be accepted without the aps-environment entitlement.

Many of the same error emails here:
http://forum.unity3d.com/threads/167574 ... ntitlement
- Me too. I’ve been told not to worry about it. I trust the person who told me so I didn’t reject the binary. One of the plugins I’m using must some push code in it somewhere.

Have a good day,

Tom

Hi Tom

Many thanks for your fulsome comments and feedback. I was beginning to think this was a one-off issue with our App but clearly is more generic!

The explanations appear to point to something within the binary checking process. Maybe this has been refined and picks up something that may have always been there in the code. I anticipate the submission process will go fine too but will post an update here in case other colleagues come across this too.

Many thanks

Dave

Me too.
Thanks for the info that I am not alone in my confusion.

Steve

Colleagues

As promised, an update. The App review process was successful so the Push Notification email appears to have been somewhat of a "red-herring".

The key phrase to focus on appears to be "if your app uses the Apple Push Notification service..."

Missing Push Notification Entitlement - Your app appears 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.

Be a lot better if we did not have to go through this uncertainty in the first place of course!!!

Dave

PS The review process was completed within 4 days. Much quicker than usual!

Hi Friends, its Tom (from above in this thread)

Me too, today, the App was approved, pretty fast, submitted on 02-05 and now ready on 02-13.

So its all as said above, no need to react to those emails and proably as said, it reads "if your app uses the Apple Push Notification service..."

So if not, then disregard the email notification.

God bless you all,

Tom

Colleagues

A further update following upload of an App. App built with LC 5.5.4. Another email notification has been received but the content has changed - see the last three sentences.

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.

Therefore, there is no need to be concerned about the email if you do not use the APple Push Notification Service. However, the last sentence suggests that LiveCode appears to include API used to register.

Is this a problem for the RunRev team to explore further?

Dave