ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid.

[hifiguitarguy]

Bug
Apple App Store Release

Environment

TFS On-Prem: Azure DevOps Server 2020 Update 1.1
Private Agent: MacOS Monterey 12.3.1

Issue Description

We have successfully used this task for other builds. We unfortunately lacked a nightly to identify a breaking change, but we generally have updated Xamarin framework targeting.

Build performs a clean sources and build output directories. I'm not familiar with where FastLane working directory is or I would dig into that further.

Xamarin.Forms 5.0.0.2515

We can build this archive and use Transporter to push to Apple manually. All I can say is we have some framework reference causing incompatibility.

Task logs

Starting: Publish to the App Store TestFlight track
==============================================================================
Task         : Apple App Store Release
Description  : Release an app to TestFlight or the Apple App Store
Version      : 1.207.0
Author       : Microsoft Corporation
Help         : [More Information](https://marketplace.visualstudio.com/items?itemName=ms-vsclient.app-store)
==============================================================================
/usr/bin/gem install fastlane
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/universal-darwin21/rbconfig.rb:230: warning: Insecure world writable dir /Users/{user}/vsts-build-agent/_work/7/s in PATH, mode 040777
Successfully installed fastlane-2.209.0
Parsing documentation for fastlane-2.209.0
Done installing documentation for fastlane after 6 seconds
1 gem installed
/usr/bin/gem update fastlane -i /Users/{user}/.gem-cache
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/universal-darwin21/rbconfig.rb:230: warning: Insecure world writable dir /Users/{user}/vsts-build-agent/_work/7/s in PATH, mode 040777
Updating installed gems
Nothing to update
/Users/{user}/.gem-cache/bin/fastlane pilot upload --api_key_path /Users/{user}/vsts-build-agent/_work/_temp/api_keyJ68VT5Z2FN.json -i /Users/{user}/vsts-build-agent/_work/7/s/{Project}.Share/{Project}.iOS/bin/iPhone/Release/{project}.iOS.ipa -a com.{SKU} --skip_submission true --skip_waiting_for_build_processing true -p 1639381866
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/universal-darwin21/rbconfig.rb:230: warning: Insecure world writable dir /Users/{user}/vsts-build-agent/_work/7/s in PATH, mode 040777
[13:35:10]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[13:35:10]: WARNING: fastlane requires your locale to be set to UTF-8. To learn more go to https://docs.fastlane.tools/getting-started/ios/setup/#set-up-environment-variables
[13:35:10]: Creating authorization token for App Store Connect API
[13:35:10]: Ready to upload new build to TestFlight (App: {AppId})...
[13:35:11]: Going to upload updated app to App Store Connect
[13:35:11]: This might take a few minutes. Please don't interrupt the script.
[13:35:11]: Apple recommends you don’t specify the -t transport and instead allow Transporter to use automatic transport discovery to determine the best transport mode for your packages. For more information, please read Apple's Transporter User Guide 2.1: https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126
[13:35:11]: Apple recommends you don’t specify the -t transport and instead allow Transporter to use automatic transport discovery to determine the best transport mode for your packages. For more information, please read Apple's Transporter User Guide 2.1: https://help.apple.com/itc/transporteruserguide/#/apdATD1E1288-D1E1A1303-D1E1288A1126
[13:35:41]: Transporter transfer failed.
[13:35:41]: 
[13:35:41]: ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{project}.iOS.app/{project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
[13:35:41]: [iTMSTransporter] [2022-08-11 13:35:41 PDT] <main> DBG-X:   parameter ShouldUseRESTAPIs = false

[13:35:41]: [iTMSTransporter] [2022-08-11 13:35:41 PDT] <main> ERROR: ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

[13:35:41]: [iTMSTransporter] [2022-08-11 13:35:41 PDT] <main> ERROR: ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{project}.iOS.app/{project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

[13:35:41]: [iTMSTransporter] [2022-08-11 13:35:41 PDT] <main> DBG-X: The error code is: 1102

[13:35:41]: [iTMSTransporter] [2022-08-11 13:35:41 PDT] <main>  INFO: Done performing authentication.

[13:35:41]: [iTMSTransporter] 

[13:35:41]: [iTMSTransporter] 

[13:35:41]: [iTMSTransporter] 

[13:35:41]: [iTMSTransporter] Package Summary:

[13:35:41]: [iTMSTransporter]  

[13:35:41]: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:

[13:35:41]: [iTMSTransporter] 	/var/folders/2l/fjzx9v4d50ldwvc_zj498nc40000gn/T/7be87dba-8ac9-4b9b-8e41-23819d261110.ipa (/var/folders/2l/fjzx9v4d50ldwvc_zj498nc40000gn/T/DeveloperAPIUpload5123279771516322553/1639381866.itmsp) - Error Messages:

[13:35:41]: [iTMSTransporter] 		ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

[13:35:41]: [iTMSTransporter] 		ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/{Project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

[13:35:41]: [iTMSTransporter] [2022-08-11 13:35:41 PDT] <main> DBG-X: Returning 1

[13:35:41]: iTunes Transporter output above ^
[13:35:41]: ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/{Project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
Return status of iTunes Transporter was 1: ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
\nERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/{Project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

[!] Error uploading ipa file: 
 [Transporter Error Output]: ERROR ITMS-90035: Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html
[Transporter Error Output]: ERROR ITMS-90035: Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/{Project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html
[Transporter Error Output]: Return status of iTunes Transporter was 1: ERROR ITMS-90035: Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/Frameworks/Runtimecore.framework/Runtimecore] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html
\nERROR ITMS-90035: Invalid Signature. A sealed resource is missing or invalid. The file at path [{Project}.iOS.app/{Project}.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html
[Transporter Error Output]: The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
[13:35:41]: WARNING: fastlane requires your locale to be set to UTF-8. To learn more go to https://docs.fastlane.tools/getting-started/ios/setup/#set-up-environment-variables
##[error]Error: The process '/Users/{user}/.gem-cache/bin/fastlane' failed with exit code 1
Finishing: Publish to the App Store TestFlight track

[kirill-ivlev]

Hi @hifiguitarguy, thanks for your request, we've added this issue to our backlog. We'll take a look at it once we have enough capacity.

[pMaske]

We are seeing this error too. Was anyone able to figure out what the problem was ? Any help is appreciated.