Скачать или смотреть Resolving the Invalid Code Signing Entitlements Warning When Updating Your iOS App

Discover a simple solution to the `Invalid Code Signing Entitlements` warning encountered when updating your iOS app with Xcode. Learn how to successfully sign your app and upload it to the App Store without issues.
---
This video is based on the question https://stackoverflow.com/q/62731624/ asked by the user 'Pelin Konaray' ( https://stackoverflow.com/u/9774694/ ) and on the answer https://stackoverflow.com/a/62745112/ provided by the user 'Pelin Konaray' ( https://stackoverflow.com/u/9774694/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: I get warning that "Invalid Code Signing Entitlements" with Apple Distribution Profile

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Overcoming the "Invalid Code Signing Entitlements" Issue in iOS app Development

As an iOS developer, you may encounter a frustrating issue when attempting to update your app on the App Store: the warning message "Invalid Code Signing Entitlements". This warning often arises due to complications with your code signing certificates and provisioning profiles. In this guide, we will break down the problem, explore its root causes, and provide a detailed solution to help you successfully sign and upload your app without errors.

Understanding the Problem

What Causes the Warning?

The warning ERROR ITMS-90046 typically manifests when the code signing entitlements your application bundle contains are not supported on iOS. For example, you might see the message indicating a problem with the key 'com.apple.developer.icloud-container-environment', specifically stating that the value 'Development' is not suitable for this key in the production environment.

Your Scenario

In the case you've shared, you faced several challenges after your certificates expired and you generated new ones. Using Xcode 11.5, you noticed:

Multiple certificates were showing up (both 'iOS Distribution' and 'Distribution').

Selecting 'iOS Distribution' led to an inability to sign the app, while choosing 'Distribution' triggered the Invalid Code Signing Entitlements error upon uploading.

A Viable Solution

The good news is that you can overcome this hurdle with a change in your app publish method. Here's how you can do it step-by-step:

Step 1: Create an xcarchive File on Your Mac

Instead of generating an IPA file on a Windows device and transferring it to Mac for upload, create an xcarchive file directly on your Mac.

Open your project in Xcode.

Select Product from the top menu.

Click on Archive.

Wait for the process to complete, which will create your xcarchive file.

Step 2: Use Xcode's Publishing Tool

Once you have your xcarchive file, you can easily publish your app using Xcode's built-in tool. Here’s how:

After your xcarchive is created, it will open in the Organizer window.

Select the xcarchive you want to publish.

Click on the Distribute App button in the right sidebar.

Choose your distribution method (App Store Connect or Ad Hoc distribution) and follow the prompts.

Sign your app with the Distribution profile (specifically for Xcode 11), making sure to validate prerequisites before uploading.

Step 3: Verify Your Certificate and Provisioning Profile

During this process, ensure that you use the appropriate Distribution (for Xcode 11) provisioning profile. In most cases, if everything is set appropriately, you should not encounter the previously mentioned error.

Step 4: Upload to App Store

After signing your app successfully through Xcode, proceed to upload it to the App Store by following these steps in the organizer tool. If executed correctly, this method should help you bypass the Invalid Code Signing Entitlements warning.

Conclusion

Changing your app publishing approach can significantly impact your code signing process and the ability to upload your iOS app to the App Store. By creating and signing your app with an xcarchive file directly in Xcode, you can avoid the pitfalls associated with code signing and ensure a smoother update process.

If you run into future issues, revisiting these steps and ensuring your certificates and provisioning profiles are correctly configured will be beneficial. Happy coding, and good luck with your app updates!