now push is in a plugin, why do I still get the warning msg?

I do not use the push function, but Apple always said I was missing it.

Missing Push Notification Entitlement

 

I hoped that now it had become a plugin it would stop giving that error message.

I mean stop giving the warning that you are missing the entitlement, even though you are not using it.

 

 

Should it have stopped?

Yes, it should have stopped.  You’re not including it for local notifications are you?

Rob

No,

Not that I know of. I never did anything with push.
I am using build 2015.2544.

What code would have been used to use it locally. Maybe I can do a search for it. I am using the GGData library, maybe it is in there somewhere?

You would have to have included the plugin.  I’ll see if I can get to a point where I can submit an app to see if I get the message.  It’s a harmless message, but since we moved it to a plugin you shouldn’t be getting it any more unless you have push turned on in your provisioning profile.

Rob

Just chiming in to say that I also am not requiring the push notifications plugin, and don’t use notifications in my app at all, but I still get the error message when submitting my app using 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.

[sharedmedia=core:attachments:3542]

I double-checked, and my app ID shows that push notifications are disabled in the iOS Dev Center. So it would seem that the plugin hasn’t yet removed whatever triggers this Apple error message. Thanks, Rob!

I have the same situation as @JufJannie and @shroederapps

I also am not requiring the push notifications plugin and I don’t use local notifications in my app. Also, the app ID does not have Push Notifications enabled.

However I still get the error message when submitting my app. I use the Xcode Organizer to Archive and then submit my apps to Apple.

Engineering is going to look into this.

Still getting this error with Version 2015.2553 (2015.2.6)

I am not using push, and have not included it anywhere in my code. Still Apple thinks I am using it.

Hi @Juf Jannie,

I think a fix for this will be available sometime this week. I will check with engineering on this matter.

Brent

Hi all,

I’ve edited the title of this post, because it’s actually a “warning” message from Apple, and not an error message. In fact it’s not even a warning. Apple sends that out when it sees your code is accessing any of the notification APIs and you haven’t included the Notification entitlement in your provisioning profile. So basically it’s saying if you intended to use Notifications, it’s not going to work, otherwise ignore this message.

In any case, this should be fixed in a daily build shortly upcoming (this week).

Thanks,

Brent

@Brent

I see that build 2015.2556 should theoretically resolve the “push” warning from Apple.

However, now I get this in the log on my iOS devices every time I start the app:

2015-02-11 23:18:29.957 myapp[13596:960397] You’ve implemented -[<UIApplicationDelegate> application:performFetchWithCompletionHandler:], but you still need to add “fetch” to the list of your supported UIBackgroundModes in your Info.plist.

2015-02-11 23:18:29.959 myapp[13596:960397] You’ve implemented -[<UIApplicationDelegate> application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add “remote-notification” to the list of your supported UIBackgroundModes in your Info.plist.

2015-02-11 23:18:30.022 myapp[13596:960397] Warning: Unable to create restoration in progress marker file

(These warnings did not show up in earlier Corona builds, and the app does not use push or local notifications)

The above app was compiled with Corona SDK 2015.2556 (Enterprise version)

OSX 10.10.2

Xcode 6.1.1

Hi Ingemar,

This shouldn’t be of concern. We’ll soon apply a fix that will suppress this warning.

Thanks,

Brent

I saw that build 2558 was released, however the Enterprise build tgz is missing.

I just get a “Page Not Found” when trying to download it.

Hi Ingemar,

This should be fixed now. Can you confirm?

@Brent

The Enterprise build 2558 still gets a “Page Not Found” when trying to download (Docs + EnterprisePlugins is OK though).

Build 2560 is OK.

Thank you for the fix. 

@Brent

Using build 2015.2560

Thanks!

The warnings in the device logs are gone on my iOS 8 devices.

Also…Yay!  The warning email from Apple is gone. 

I’ve submitted a few updates to Apple today, and none of them generated the “Push warning” email.

Yes, it should have stopped.  You’re not including it for local notifications are you?

Rob

No,

Not that I know of. I never did anything with push.
I am using build 2015.2544.

What code would have been used to use it locally. Maybe I can do a search for it. I am using the GGData library, maybe it is in there somewhere?

You would have to have included the plugin.  I’ll see if I can get to a point where I can submit an app to see if I get the message.  It’s a harmless message, but since we moved it to a plugin you shouldn’t be getting it any more unless you have push turned on in your provisioning profile.

Rob