LiveCode Forums.

All,

I am using local notification in my app. I am not using push notifications. I submitted a new version of the app onto the app store yesterday and then got the following error which I don't understand given I am only using local notifications. Anyone help?

We have discovered one or more issues with your recent delivery for "Forget me Knot Reminders". 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 reject this binary from the Binary Details page in iTunes Connect. Note that rejecting your binary will remove your app from the review queue and the review process will start over from the beginning when you resubmit your binary.

Paul...

I submitted an app for review the other day and got the same message after it was uploaded... In this app I am not employing either 'local' or 'push' notifications. This seems to me to have only appeared since Apple updated their iTunes connect pages... I noted that it was only a warning, so am hoping that it will not be an issue with getting the app accepted...

Having said that... time will tell ..

Dixie

I did a general trawl of the internet and the consensus was that this was a general error and an issue with an update to iTunes Connect.

I did not get the issue when I submitted the original version on the 1st March and it was then approved a week later. Btw, thank you to runrev for no review issues in my first app submission.

I do however an issue with the splash screen when download the app from iTunes. I believe the issue is due to incorrect naming of the Splash screens. I have now corrected this.

Dixie - can you let me know if you have an issue with Splash screens when your app is on iTunes?

Paul...

I have 4 apps in the iTunes store at the moment and none of them employ a splash screen... since there is not much going on when the apps load, I decided not to bother ... so, I am afriad I can't help you there

be well

Dixie

My app update got accepted by Apple so it seems the issue was an issue with iTunes connect as opposed to my app.

I recently submitted a new app (May 24, 2013) and received an email from Apple stating that my app includes a call to the API used to register with Apple's Push Notification service. See the message below:

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.

Non-PIE Binary - The executable '<app nname>' is not a Position Independent Executable. Please ensure that your build settings are configured to create PIE executables.

If you would like to update your binary for this app, you can reject this binary from the Binary Details page in iTunes Connect. Note that rejecting your binary will remove your app from the review queue and the review process will start over from the beginning when you resubmit your binary.

Regards,

The App Store team

FYI, I am running LC 5.5.5 (with the UDID bug fix) and mobGUI 0.29. So, it appears that my app is still in the queue for review and this message from the Apple is to be interpreted as a warning. I'll post updates as status changes. Hopefully this is a minor issue and doesn't stop us developers from submitting our apps.

Here's to a quick resolution... Judoka

theagilepad wrote:All,

I am using local notification in my app. I am not using push notifications. I submitted a new version of the app onto the app store yesterday and then got the following error which I don't understand given I am only using local notifications. Anyone help?

We have discovered one or more issues with your recent delivery for "Forget me Knot Reminders". 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 reject this binary from the Binary Details page in iTunes Connect. Note that rejecting your binary will remove your app from the review queue and the review process will start over from the beginning when you resubmit your binary.

The same here.

The RunRev people already know ...
... this is the answer from the support :



We are aware of this issue and a bug report has been created which will allow us to
investigate it further-

http://quality.runrev.com/show_bug.cgi?id=10979

In the mean time, this warning message can be ignored and you can continue with the
app store submission process.


Guglielmo

Thank you Guglielmo

Mag wrote:Thank you Guglielmo

You're welcome!

Got it too. To do with sound playing (notification api?)?