I am pretty certain that it is a bug in Apples checking system. I uploaded an app yesterday and got this message. This app has been updated at least 30 times without any problems. I didn’t add any push notification code in the last version and I don’t use any frameworks like PhoneGap or Cordova that could cause this message. It doesn’t appear under notifications on the device.
I have searched the app for push notification code without finding anything:
grep -r “registerUserNotificationSettings” .
grep -r “registerForRemoteNotificationTypes” .
I finally tried to upload the previous version that was approved in July (and didn’t generate an email). This this time I got the warning email also for this version. So I think that Apple is wrong and I will take my chances and hope it will be approved despite the warning.
EDIT: Found this reply from an Apple staff in Apple Developer Forum:
“That notice is a warning only, not a rejection.
The app validator checks for an implementation of the UIApplicationDelegate method application:didRegisterForRemoteNotificationsWithDeviceToken: in the app. You’ll get the warning you described if your app delegate implements that method and there is no aps-environment entitlement.
It’s possible that a third-party library you’re using has implemented that method even though your app doesn’t do anything with push notifications. In that case you can just ignore the warning. It’s there to let developers who do use push notifications know if they might have signed their app incorrectly.”
EDIT 2: I now have two different apps that have been approved without any problems despite generating the warning email