-
Notifications
You must be signed in to change notification settings - Fork 54
Explicit provisioning_profile_path not used? #69
Comments
It should be used in this command
but it looks like only the code signing identity was added. I'll need to take a closer look on why this isn't set. I assume you're using |
Yes, I'm using Eventually I went with the Thanks! |
I'm seeing the same thing. It appears that |
It seems like it's working for me. Could you try using the latest version and show the complete output while running |
Using gym version Fastfile: gym( provisioning_profile_path: "./path/to/MyApp.mobileprovision" ) Output: set -o pipefail && xcodebuild -workspace '[Redacted].xcworkspace' -scheme '[Redacted]' -destination 'generic/platform=iOS' -archivePath '[Redacted]' archive | xcpretty Provisioning profile never makes it into the My current workaround is to just forward the GYM ENV vars for identity or profile through via gym( xcargs: "CODE_SIGN_IDENTITY='#{ENV["GYM_CODE_SIGNING_IDENTITY"]}'" ) |
Same here
After archiving, I can see that the ipa is not using the mobileprovision provided in the Cheers. |
@dmiotti If you use Xcode 7 you should get this message: Helper.log.info "You're using Xcode 7, the `provisioning_profile_path` value will be ignored".yellow
Helper.log.info "Please follow the Code Signing Guide: https://github.com/KrauseFx/fastlane/blob/master/docs/CodeSigning.md".yellow as this option was deprecated by the |
Do I understand right, that instead of I mean:
Or: Thanks! |
@yakimant Have you seen the code signing guide? It should clarify your question. |
@KrauseFx, I've read it multiple times, believe me ;) But there is no information about Thank you! |
The option is not used in the latest version of |
This still doesn't make sense to me. The code signing guide referenced here has everything listed as deprecated, the new one says "just create all the certs for each type of build and magic happens" (paraphrasing). Unfortunately, my "Debug" build and "Release" build both use the same distribution certificates. How do I tell FWIW, the docs for
If I do add (Sorry if my tone is grumpy, I'm frustrated...mostly at myself because I think I'm missing something!) |
@KrauseFx what is defaults if I'm not using match. Does gym select provisioning profile based on configuration in xcode? I'm running a issue that fabric complaining device ids missing after submitting a build by gym. |
Interesting - I'm having the same issues that @yakimant and @MadNik . It seems that even if you set:
The build itself is fine, in the archive the correct provisioning profile can be found; but the export from archive operation takes the provisioning profile from |
You should use match which will tell you how to setup your Xcode project: https://github.com/fastlane/match#setup-xcode-project |
I switched to using this and it appears to work. (note: added sigh to the
Probably the most confusing is that even though I used |
@knitterb-razzle that's Xcode magic then, it will automatically choose the right profile sometimes., I'd recommend setting it in the project like described in the |
This issue was migrated to fastlane/fastlane#1866. Please post all further comments there.
|
I'm using
gym
to build an enterprise version of our app. Just for this task it should use an explicitly provided provisioning profile and code signing identity, that override the ones defined in the project.I'm building with the
--verbose
flag since after the first try I saw that it was using the wrong (as defined in the Xcode project) provisioning profile instead, but it looks like the generated build command doesn't include any parameter for passing the specified provisioning profile.Is there any step I'm missing?
Generated build command:
The command I used is:
After
xcodebuild
finishes, I got the following command:But nowhere I can see the embedded provisioning being set.
The text was updated successfully, but these errors were encountered: