Signing 3rd party .framework bundled in the app

Hi,

I use a 3rd party/open source framework. I embedded its project in my main app's project, and I set my main app to be dependent on it. I can build, deploy and run my app in the test device using developers profile in xcode. The problem is when I try to build it from command line for distribution. I tried passing the adhoc cert and adhoc provisioning profile as parameters. It is complaining that the bundleId of the framework is different than the one defined in the provisioning profile. Which is obviously true because the bundleId of the framework is pre-defined by its developer.

I use this command to build it:

xcodebuild build -workspace <my wrkspace> -scheme <scheme> CODE_SIGN_IDENTITY="<identity name>" PROVISONING_PROFILE="<provisioning name>"CODE_SIGNING_REQUIRED=“YES” CONFIGURATION_BUILD_DIR=<path>


The options that I can think of:

1. Change the bundleid of the framework to match my app bundleid

2. Do not sign when building, but pass the provisioning profile when exporting an .ipa. Assumming that xcode will use the correct signing cert that my provisioning profile specified

xcodebuild -exportArchive -exportFormat ipa -archivePath <xcarchive filename> -exportPath <.ipa filename> -exportProvisioningProfile <provisioning profile name>


Any advice will be highly appreciated.


Thanks

Hi,


I got the same issue with when building ipa through Jenkins(CI). Your solutions inspire me a lot. Thanks.

How do you resolve this at last? Any better ideas? Thanks.

We're also seeing this issue when using CI, did you find a solution?

Signing 3rd party .framework bundled in the app
 
 
Q