Detect the presence of the "Resources" folder when signing and show an helpful error. #20135
Comments
rolfbjarne
added
enhancement
|
I am getting same issue. I have tried all soloutions provided but no luck. I really dont know why this is happening. I moved to MAUI for easyness of coading. Now its getting nightmare. Even I am not having resources folder in iOS Project. I have removed all referenace in project file. /usr/bin/mdimport bin/Release/net8.0-ios/ios-arm64/ Warning: unable to build chain to self-signed root for signer "Apple Distribution: XXXXXXXXXXXXXXXXXX" C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8004\tools\msbuild\iOS\Xamarin.Shared.targets(2256,3): error : /usr/bin/codesign exited with code 1: [C:\Users\ANUP\source\repos\NewDuaHealingsApp2\NewDuaHealingsApp2.csproj::TargetFr |
This might help: https://blog.verslu.is/app-publishing/unable-to-build-chain-for-self-signed-root/ |
…es subdirectory. Fixes xamarin#20135. iOS (and presumably tvOS) app bundles can't contain a subdirectory named "Resources". Apple says: > Note: An iOS app bundle cannot include a custom folder named “Resources.” Ref: https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html#//apple_ref/doc/uid/10000123i-CH101-SW1 Unfortunately Apple's toolchain won't show a helpful error message, the eventual failure is codesign saying something like this: bin/Release/net8.0-ios/ios-arm64/SomeApp.app: code object is not signed at all In subcomponent: bin/Release/net8.0-ios/ios-arm64/SomeApp.app/System.Security.Cryptography.aotdata.arm64 Which is confusing, to say the least. After debugging this myself a few times, and seeing customers running into the same issue periodically, it's time to make the error more actionable. I've added code to our Codesign task to detect the "Resources" subdirectory, and show a better error message. There's also a way to disable the validation (by setting `CodesignDisallowResourcesSubdirectoryInAppBundle=false`), just in case we end up being overeager with the validation. Fixes xamarin#20135.
…es subdirectory. Fixes #20135. (#20593) iOS (and presumably tvOS) app bundles can't contain a subdirectory named "Resources". Apple says: > Note: An iOS app bundle cannot include a custom folder named “Resources.” Ref: https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html#//apple_ref/doc/uid/10000123i-CH101-SW1 Unfortunately Apple's toolchain won't show a helpful error message, the eventual failure is codesign saying something like this: bin/Release/net8.0-ios/ios-arm64/SomeApp.app: code object is not signed at all In subcomponent: bin/Release/net8.0-ios/ios-arm64/SomeApp.app/System.Security.Cryptography.aotdata.arm64 Which is confusing, to say the least. After debugging this myself a few times, and seeing customers running into the same issue periodically, it's time to make the error more actionable. I've added code to our Codesign task to detect the "Resources" subdirectory, and show a better error message. There's also a way to disable the validation (by setting `CodesignDisallowResourcesSubdirectoryInAppBundle=false`), just in case we end up being overeager with the validation. Fixes #20135. --------- Co-authored-by: Manuel de la Pena <mandel@microsoft.com>
If an iOS or tvOS app contains a
Resourcesfolder, codesigning fails with a very unhelpful message:And this causes a lot of confusion (ref: dotnet/maui#20640).
We should detect the presence of a
Resourcesfolder before trying to sign, and show an error (we should probably allow the user to opt out of the error in case we get something wrong or Apple changes their logic at some point).References:
The text was updated successfully, but these errors were encountered: