-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS #270
Comments
Hi @EmilAlipiev seems like there are some not supported code signing entitlements specified for your app (like 'Production') - see more in apple docs. |
@EmilAlipiev please ping if you have any other questions |
@anatolybolshakov thanks for your reply. I am not sure where do you see that aps-environment with value Production as entitlement cant be set. I have already googled and cant find anything related. On the other hand, app signing is working just fine through XCode with this entitlement. That confuses me. |
@EmilAlipiev did you manage to upload the same app package manually to app store? |
@anatolybolshakov yes, i do using xcode directly to appstore without any problem. |
@EmilAlipiev could you please share your pipeline yaml file to take a look? |
@anatolybolshakov I am not doing anything specific with the Yaml. I think that it can simply reproduced by adding an entitlement with |
@EmilAlipiev we are unable to reproduce this issue. This could be probably related to some difference between configuration and build process of your project in pipelines and local environment. We also don't see any signs of issue on task side here - there is an 'Invalid Code Signing Entitlements' error coming from iTunes Transporter which says that there are code signing entitlements in application bundle's signature which are not supported by iOS platform. |
On Azure Pipelines my Xamain.Ios build returning this error
I found the similar issue on fastlane github but when I followed the suggestion on the issue below, error persists
fastlane/fastlane#768
Not sure if this suggestion is valid for VS4Mac as well. I have simply set the signing as Manuell and selected correct publish profile.
I have tested with resigning and without but same error always.
Normal build, package and deploy using Visual Studio and Xcode on Mac works just fine but only in Azure Devops with this extension.
Do you know what might be the root cause and if there is any workaround?
The text was updated successfully, but these errors were encountered: