Missing push notification entitlements

App & System Services Notifications User Notifications

gilsongil OP

Created Jul ’15

Replies 38

Boosts 0

Views 13k

Participants 34

Hi,

I am uploading an app to itunes connect but I always get the "Missing push notification entitlements" email.

I triple checked everything from my certificates, to app id, provisioning profile, but everything looks fine.

I installed through Testflight but was getting "didFailToRegisterForRemoteNotificationsWithError", so I know it's not working.

The problem is that installing the same build through Crashlytics distribution platform, I was succeeding at registering for remote notifications.

How is that possible? What am I doing wrong?

Thanks,

Answered by gc. in 47536022

If your app does not use push notifications, it is completely safe to ignore the warning. It's there to let developers who do use push notifications know that they might have signed their app incorrectly.

There was an issue with the app validator the week of August 31, 2015 that caused this warning to be sent erroneously to some developers whose apps do not use push notifications. This issue was corrected on September 2. The next time you validate or submit your app you should not see the warning.

--gc

Boost

tilllate OP

Aug ’15

Also received this warning by email. I uploaded my app 2 weeks ago and there was no warning, yesterday changed my code a bit (not related to push notifications at all and not including any new libs) and received the warning.

lucaslt89 OP

Sep ’15

I also have the same issue. My app doesn't use APNs at all, nor implements any of remote notifications related methods. I use Fabric/Crashlytics, but I'm using it since the beginning of my projects (two months ago) and I never had this warning until last week.

I'm also able to install the app from TestFlight, without any problems.

Maybe it's just an iTunes Connect issue, but couldn't this block the app to be released to the AppStore?

Jae OP

Sep ’15

I have this same problem. I just started using Fabric and then I got the email warning when uploading the new binary.

gc. OP

Sep ’15

Accepted Answer

--gc

mathaeus.zingerle OP

Sep ’15

I also got the warning (although APN is not configured) but nevertheless submitted the app now for review.

mjmsmith OP

Sep ’15

I have the same problem with an app that has never used push notifications (although it does use Fabric/Crashlytics). Is there any way to stop the email going out to all TestFlight internal testers when a new beta is uploaded? Even if it was a real problem, I don't understand why it goes out to the entire list.

dontangg OP

Sep ’15

I am still seeing this happening. I just barely went back to the exact version that I submitted a couple weeks ago (and released to the App Store), and I still get this warning when I submit that build.

surajqwe12dasd OP

Sep ’15

It's Sep 4th now, and I am still receiving this warning when I submit my code to iTunes Connect for testing. I have checked my code and no where have I used push notifications. I am worried about my app being rejected because of this as we do have a tight schedule.

NikOs OP

Sep ’15

The issue is still present as of September 4.

vinay.plutocrat OP

Sep ’15

But I still face same issue on 4 september 2015 , please help us.

jcasier OP

Sep ’15

Yes, I am seeing this happen also. It's also very annoying that this email is going to all iTunes connect users on the account, even the disabled ones

mnifield OP

Sep ’15

I am getting this warning again now. Could you look into it again?

CCS Technologies OP

Sep ’15

We have uploaded a binary Yesterday (11/Sep/2015) and still we are getting the same warning. Is this not corrected yet?

databyte OP

Sep ’15

I'm getting the emails again since September 14th...

Joos OP

Sep ’15

Same issue here. 9/15/2015 ... Anyone get around this yet? Can someone from Apple shed some light?