Missing Push Notification Entitlement

[myflashlab]

We have recently received some news about devs receiving a warning like the following when submitting there apps to app store.

Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service.....

It seems like this is happening because of iOS 10 new requirement that the uploader tool can see the code being used in ANEs. For example, in your app, you may not be using the remote notification at all but the overrideAir ANE is using some listeners like application:didRegisterForRemoteNotificationsWithDeviceToken:. Although not being used by you, apple seems to need the Entitlement tag to be available in your manifest air .xml file anyway.

This problem is very similar to the other news that AIR devs have reported when using the permissionCheck ANE check out the ticket here.

Our investigation shows that developers in other multiform environments are also experiencing a very same problem. One example is this link: https://stackoverflow.com/a/45207458/247658

So, the current work-around is to add the required entitlements to your app. i.e, activate push notification in your apple console and also add the entitlement tag to your air .xml file. This way, the warning will be removed. The good thing is that when you activate the push notification and the entitlements tag, it does not mean that you really need to use them in your app! Your users will be alerted with the notification permission ONLY if you are using the FCM ANE and call FCM.init();.

We are keeping this issue open so devs can share their experience about this problem. The more information we would have on this, the easier we can find a solution for it.

[raresn]

I get the same warning. I`m using: <extensionID>com.myflashlab.air.extensions.dependency.androidSupport</extensionID> --> <extensionID>com.myflashlab.air.extensions.dependency.overrideAir</extensionID> <extensionID>com.myflashlab.air.extensions.statusbar</extensionID>

[myflashlab]

Ok, the problem and the workaround are all explained in the first post. I'm not sure what is your question so I can help.

[raresn]

I was just sharing my experience with this problem :)