Error signing framework directory
Closed this issue · 3 comments
I tried wrapping the app with the iOS wrapping tool and got an error about signing the framework directory.
Mac OS Version: macOS Ventura 13.4.1
Xcode: 14.3.1
Wrapping Tool: 17.6.1
If anyone knows anything about the cause please let me know.
Also, is there any other information you need?
Below is the log.
Thanks.
Warning: Warning: You must specify an AAD reply URI.
Warning: WARNING: By default, the Microsoft Intune App Wrapping Tool changes the build string of the target app to help ensure it can be successfully deployed as an upgrade should you decide to wrap the same version/build of the app with a newer version of the wrapping tool (to take advantage of new features). Use of the build string override option (-b) is only recommended if testing revealed some issue in app deployment or functionality caused by the default changes to the build string. For more information on iOS app versions (CFBundleShortVersionString) and build strings (CFBundleVersion), visit https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html#//apple_ref/doc/uid/TP40012582-CH28-SW18
Message: Application packaging in progress...
Verbose: Version of MACOSX is 13.4.1
Verbose: Version of XCode installed is Xcode 14.3.1
Build version 14E300c
Verbose: Parsing provisioning profile...
Verbose: Parsing main app provisioning profile...
Verbose: Parsing extension provisioning profiles...
Verbose: Checking that main provisioning profile has not expired...
Verbose: Checking that extension provisioning profiles have not expired...
Verbose: Checking if signing certificate is valid...
Verbose: Number of certificates returned by query: 1
Verbose: Checking certificate at index: 0
Verbose: Getting certificate common name.
Verbose: Possible name match found. Checking if certificate is contained in provisioning profile...
Verbose: Computing SHA-256 fingerprint of certificate.
Verbose: Checking if SHA-256 hash exists in provisioning profile.
Verbose: Certificate was found in the provisioning profile.
Verbose: Checking if certificate issuer is Apple.
Verbose: Checking if signing certificate is found in each extension profile...
Verbose: Creating temporary directories...
Verbose: Input Parameters
Path to input application: /Users/t81640765/Desktop/ProvisioningProfileUpdateWork/APP/202307/23.0.1.1893_APP_Corp.ipa
Path to output application: /Users/t81640765/Desktop/ProvisioningProfileUpdateWork/APP/202307/23.0.1.1893_APP_Corp_20230718.ipa
Provisioning profile: /Users/t81640765/Desktop/ProvisioningProfileUpdateWork/APP/202307/APP.mobileprovision
Certificate: iPhone Distribution:
Warning: WARNING: This application supports opening one or more file types, but does not have the appropriate entitlements to be supported with Intune APP. An additional provisioning profile needs to be specified using the -x command line argument. This profile must have a wildcard application-identifier or must have an application-identifier of 'jp.co.Corp.APP.IntuneOpenInAction' and must contain at least one application group which is shared with the main application. If this profile is not specified, other Intune APP enabled applications will not be able to send files to this application.
Error: The app's Frameworks directory could not be signed. This may be because it contains files whose format was unrecognized, invalid, or unsuitable.
Cause of the error to be provided for investigation:Error Domain=IntuneAppPackager Code=1 "/usr/bin/codesign exited with an error." UserInfo={Error Description=SignFrameworksError, NSLocalizedDescription=/usr/bin/codesign exited with an error.}
Hi @pom0416. Can you try to manually run codesign on each of the .dylib files and .framework directories within your app's Frameworks directory to see which one is causing the issue?
The command is:
/usr/bin/codesign --force --sign "CERT_HASH" --options expires PATH_TO_DYLIB_OR_FRAMEWORK
Replace "CERT_HASH" with the certificate hash you passed to IntuneMAMPackager for the -c argument.
Thank you,
Neil
Hi, @neiljac1
I checked with the command you sent.
It was because the certificate I was using was not trusted.
solved.
thank you.
Great. Glad the issue was solved.