All geek questions in one place

Missing aps-environment in the configuration profile!

For some reason, our adhoc provisioning profile simply won’t have aps-environment permissions! We made sure that the profile is created after we activated apn for this application identifier. We even created a new adhoc profile for this application identifier, and even if the new profile does not have this right when checking with a text editor. What's happening?

+4
source share
4 answers
  • Make sure the package ID matches the one in your project.
  • Create a new application identifier and configure it to create / create before creating a new provisioning profile.
  • Make sure you build and archive to the right target with the correct configuration. You may need to go back to the project settings and double check with the correct configuration selected (for this I use release).
+9
source

If, after regenerating this profile and / or creating a new right, it is still missing, this seems like an error on the iOS Portal website (server side).

Contact the developer programs for help or explanation (not counted for DTS TSI). Use the "Program Benefits" link on this page, as it is "for questions about creating training profiles ..." For others, please note that after the application ID has new permissions (for example, when Push Notification is enabled for of this application identifier), you must manually restore all associated profiles in order to obtain new profile rights. Do this on the iOS Portal Provisioning page, Development or Distribution tab (as appropriate). Go to each profile and restore them by clicking "Edit" or "Change." Something needs to be changed on the editing page to enable the Submit button, so for the distribution distribution profile, temporarily switch the distribution method from the "App Store" to "Ad Hoc" and then back. Then click Submit to update your profile.

+5
source

Make sure your local rights file does not contain additional keys, for example. APS medium.

There is no error on the Apple Portal. I fixed this problem at the end by removing the aps-environment key from my local rights file. Xcode seems to be doing a preliminary check by comparing your rights files with the installed provisioning profiles. If he sees something in your rights file that is not in your profile, then the action that he lists in the compilation error is to add the missing profile right. However, instead, it should be said that your rights file matches your profile.

Therefore, this seems to be an error in the process of checking the Xcode profile.

0
source

I added this to my rightlements.plist file and you're done.

<key>aps-environment</key> <string>production</string>
0
source

Source: https://habr.com/ru/post/1340103/

More articles:


All Articles