Invalid Push Code Signing Rights (ITMS 90046)

I get an error when trying to send an update to an iPhone application through Application Loader. I didn’t change anything in the configuration since I did the last update, so I'm not sure why he is complaining now.

I tried updating the provisioning profiles in Xcode, and also tried to explicitly set the Provisioning Profile in the project build settings. When explicitly setting the Provisioning Profile in Build and then doing Archive, Xcode complains that “There are no matching code signing identifiers” for the selected provisioning profile. When I do a Fix Issue, Xcode resets the Provisioning Profile in the build settings back to Automatic and Code Signature Identification on iPhone Developer.

I also tried to perform a clean build, Alt + Clean, to clear the build folder, restart Xcode several times, and did "Delete by derived data in the organizer"> "Projects", but nothing helped.

"ITMS-90046 ERROR:" Invalid code signing rights. The signature of your application package contains code signing rights that are not supported on iOS. In particular, the value "development" for the key "aps-environment" in "..." is not supported. "

When I try to send an archive after Xcode automatically resets the code signing identifier in iPhone Developer, I get the following error.

I might try to revoke the distribution certificate, but I'm not sure what the consequences will be. The Apple website says that certificate revocation does not affect existing apps in the store, but I am worried if there are any other unforeseen consequences of this that I did not think about.

“Failed to find or create matching signature assets: Xcode tried to find or create matching signature assets and was unable to do this because of the following issues. Your account already has a valid iOS distribution certificate. If you have a signature ID on another Mac you You can import the developer profile, or you can cancel the current certificate and request it again.

Any help would be greatly appreciated.

+6
source share
3 answers

Try performing Product-> Clean, and then verify that the Provisioning profile and code signing IDs are correct.

code signing details

+11
source

I found this problem because during development I tried to reuse the package identifier. This was solved by checking the installation of the assembly> product identifier and correcting the name, the same as the package identifier. I think xcode does not replace this newest newest package identifier. I hope this help

0
source

Ideally, Xcode should automatically understand this and override the standard "development" of aps-enviroment, in reality it often does not work.

The easiest way out of this nightmare is to copy the rights file, name it Release.entitlements - and tell it about the build settings.

This fixed it for me.

-1
source

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


All Articles