Dear Lukas, Thanks for the detailed answer ad the good luck wishes, looks like we need it. We will look into 5 (I guess something similar is described in http://stackoverflow.com/questions/27973011/xcodebuild-different-provisioning-profile-for-target-dependency/29605731#29605731)
Best, Roman Am Dienstag, 22. September 2015 17:58:47 UTC+2 schrieb Lukas Mollidor: > > Hi Roman. > > Here's a couple of ideas that have helped us in the past. > > 1) Try to limit the options Xcode can choose from > The fewer options Xcode has, the better. Delete all outdated provisioning > profiles and only import the ones you really need (see 3). Try creating > different Jenkins slaves that only have the exact set of signing identities > and provisioning profiles you want Xcode to use. So you could create a > slave that has the distribution cert and only the ad hoc provisioning > profiles. You can then use labels to make Jenkins build Ad Hoc builds on > your "Ad Hoc Slave". Combine with (3). Be aware that Xcode might require > valid development credentials as well and otherwise fail the "check > dependency" phase. Feel free to file a rdar... > > 2) Do not set a provisioning profile > Do not enter a provisioning profile's ID in "Embedded Profile". If set, > Xcode will try to sign every target using this profile and most likely fail. > > 3) Avoid wildcard profiles > Although it's a painful process, create a dedicated App ID and > provisioning profile for every single app and extension. If Xcode has less > choices chances are higher it chooses the right one. > > 4) Set the Code Signing Identity > If Xcode happens to use development certificates you can force it into > using the distribution identity by setting the "Code Signing Identity" or > CODE_SIGN_IDENTITY="iPhone Distribution: YOUR TEAM" in "Custom xcodebuild > arguments" when using xcodebuild > > 5) Create a dedicated configuration for Ad-Hoc builds > If you can not make Xcode choose the correct one automatically, try > creating a dedicated build configuration for Ad Hoc builds (i.e. adhoc). > You will then be able to set a specific provisioning profile for each > target for this configuration (as opposed to Xcode choosing one). If Xcode > can not find that profile the build should fail, which is not great but > still better than finding out when trying to install/submit. You can set a > different bundle identifier as well which would allow for installing your > Ad Hoc build and your App Store version side by side on the same device. > > Good luck, > Lukas > > > Am Sonntag, 20. September 2015 11:59:08 UTC+2 schrieb > [email protected]: >> >> Hi there! >> >> We are trying to build our ios-application using the xcode-plugin and >> receive the following error when trying to install it on ios>7 via Xcode: >> The entitlements specified in your application’s Code Signing Entitlements >> file do not match those specified in your provisioning profile. >> >> While the right embedded profile is used for the app itself(Ad Hoc), the >> wrong embedded profile is used for the extensions (App Store). >> >> Any hints? >> Best, >> Roman >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/63116310-388c-466f-a641-f2c4ba56cc1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
