Missing Push Push warning warning

Question

We have created an application identifier, distribution certificate, and provisioning profile. Push Notifications were not originally included.

Now we need to implement Push notifications in the application.

We have enabled push notifications in Appendix D, check the provisioning profile, the provisioning profile is invalid, update it, and download the latest provisioning profile to use it next time.

Then we integrate the API for push notifications via APNS in our code.

After downloading the application to iTunesConnect, we receive the following email from Apple:

Dear Developer,

We have encountered one or more problems with your recent delivery to Swanvi. Your delivery was successful, but you can fix the following problems with the following delivery:

No Push Transfer Notification Rights - Your application appears to include the API used to register with the Apple Push Notification service, but the application’s signing rights do not include the “aps-environment” rights. If your application uses the Apple Push notification service, make sure your application identifier is enabled for Push Notification in the Portal Provisioning Portal and resubmitted after signing your application with a distribution profile that includes the “aps-environment” access right. See the Prevention and Development section of the Local and Push Notification Programming Guide for more information. If your application does not use the Apple Push Notification service, no action is required. You can remove the API from future views to stop this warning. If you use a third-party structure, you may need to contact the developer for information about removing the API.

After troubleshooting, you can use Xcode or Application Loader to upload the new binary to iTunes Connect.

We re-checked the application identifier. Push notifications are included for development and production.

The Provisioning Profile displays the Push Notifications button.

Why do we receive this warning email?

Answer 1

You need to see 2 things: the provisioning profiles used by your Xcode account and those listed on developer.apple

All about provisioning profiles.

STEP 1 : Go to https://developer.apple.com/account/ios/certificate/ and view the Active Provisioning Active Pro profiles for your application. Then click on it and make sure Enabled Services Push Notification . If this is not the case, click on edit and enable it by following the steps provided by Apple. If it is on, it’s perfect.

STEP 2: Remove all Invalid Provisioning Profiles that you see associated with the application (only invalid for your application). I will tell you why in the next steps.

STEP 3: go to Xcode → Preference → View details (for your account) → [OPTIONAL: to make sure that there is no invalid, rt-click on any provisioning profile, select “Show in Finder”, then Delete / Move all provisioning profiles from this folder.] Now click "Download All Profiles". This will replace the local provisioning profiles with current ones. Press DONE.

STEP 4: Go to your application Goals → Build Settings → In the code signature, expand the Provisioning Profile to display the Debug and Release tabs. By default, it will be turned on automatically (therefore, your application will probably automatically use an invalid profile that we just deleted in step 2). For Release , to be on the safer side, select the Active Provisioning Profile with the Push Notifications enabled, as shown in step 1.

It.

Now you should not receive emails.

Answer 2

@Djeeraj VS is true. Cordoba added some conditional compilation to remove this requirement for applications that do not need push notifications.

You can comment on the code in Classes\AppDelegate.h according to this answer , but it's better to add the compilation symbol DISABLE_PUSH_NOTIFICATIONS through the user interface so that you can continue to take advantage of future updates of Cordoba.

I come from .NET, so I'm familiar with conditional compilation, but I had to spend a bit of time developing how to get the flag of a compiler running in Xcode.

Invokes the magic word here: "Macroprocessor macro." Here's how to do it graphically through the user interface (note that this is the way it is done in Xcode 6.1):

Hope this helps other people in the same situation.

Answer 3

In my case, I just checked the "Opportunities" page in the project properties again and clicked "Fixed a problem" in the corresponding APNS menu. Now it should look like this

Xcode 11. To process, click on the Capability (+) button

Answer 4

I had the same warning, and this is how I solved it.

First of all, when you archive your project under permissions, if you do not see aps-environment , and your application uses push notifications, you will receive the warning mentioned in the question.

FIXES STEPS

1- Make sure your distribution profile is valid in the Apple Portal. - If not, then regenerate it. 2- If your distribution profile is valid, then in Xcode, go to Preferences , and then click View Details . At this point, in the Profile Profiling section, make sure that you do not have invalid files for preparing backups. If there are invalid ones, right-click and move them to the trash. If you do not have a valid one, download it from the portal. 3- Go to Assembly Settings → Code Signing , and for everything, select a distribution provisioning profile.

At this point, if you are archiving, you can see the aps-environment in your rights, and a warning will not appear.

Answer 5

In my case, the following practice worked. Xcode 9.2

• Disabled Automatically manage signing , which appears in Build Target > Signing
• Import a provisioning profile manually.

Answer 6

I have a Cordova application where I had notifications before, but I wanted to remove it from the application. I tried to follow the answers above, but still ran into this problem when loading the assembly. I realized that I had a plugin installed that used the notification setting and somehow left some settings activated for notifications.

I solved the problem by completely removing the ios cordova platform rm ios , adding it again to the cordova platform add ios and making sure the plugin was removed from the ios.json and fetch.json .