Code signing fails for Enterprise distribution #90
Comments
|
Thank you so much for your very detailed report. Could you try updating to the latest or in your sigh(export_method: 'enterprise')More information: https://github.com/fastlane/gym/releases/tag/0.7.0 |
|
Wow that was fast @KrauseFx! 🚀 Unfortunately I'm still getting an error, but it is different now:
I'm still building with Fastlane, therefore the revalant part of my |
Does building + exporting work with Xcode? |
|
Yes, archiving and exporting works in Xcode. Note that when I export from the Organizer, I get this Device Support screen.
I'm not sure if that has anything it do with the |
|
@KrauseFx This may help: https://forums.developer.apple.com/thread/13446
|
|
You mean |
|
That's what I'm doing right now hash = { method: Gym.config[:export_method] }
if Gym.config[:export_method] == 'app-store'
hash[:uploadSymbols] = (Gym.config[:include_symbols] ? true : false)
hash[:uploadBitcode] = (Gym.config[:include_bitcode] ? true : false)
end |
|
It looks like that may be the case. At least according to the
But I tried manually editing the plist file adding a And it still didn't work when I re-ran the command:
I see nothing related to |
|
It's interesting that the Oh Apple... is there an easy way to determine what Xcode's Organizer is doing under-the-hood? |
|
Okay, after digging and digging into the log files in the So, I tried running this myself in terminal and I got an error message indicating the I'm using So, it appears that using It's a shame I have to switch to the system Ruby ( Edit: It looks like you can do TL;DR: |
|
Very interesting, thanks for taking a closer look. I'm using both I'm glad you found a way to get it working! 🚀 |
|
@KrauseFx Do you have the I guess you can consider this issue closed now. Unless you have a way of forcing |
|
@djtarazona I think that forcing them to use system Ruby is not the right call. Probably it's better to add |
|
@marcelofabri Ya I thought about that. My concern is that Apple's |
|
I was running into the same issue ("No applicable devices found."). |
|
I'm running into a similar issue, and running Is there any documentation for all of the gym options (as used through fastlane), what they mean, and which ones you should use on Xcode 7? Edit: For now I've switched back to ipa (wow it's slow) to build our Crashlytics archives. |
|
I just pushed a new release https://github.com/fastlane/gym/releases/tag/0.7.1, basically you can fallback to the old way of code signing using the |
|
@jshier please try |
|
@KrauseFx Thanks, that works. I can switch back to gym and cut my ipa build times in half. |
|
🚀 💪 |
|
Hi @KrauseFx thanks for this awesome tool.
|
|
@NikhilRyan Did you add the |
|
@truth3 thanks for the reply. I just tried |
|
@NikhilRyan I don't have the specifics, but If you see Felix's reply a couple days ago.. it will revert back to the old way of code signing (I believe more specifically on the export action). Outside of that, all I know is that it works 👍 |
|
Are you trying to export for AdHoc? if so, make sure to pass the Basically the new way to code sign and export your app with Xcode 7 works for most setups but might cause some issues as it does additional verifications. |
|
Use whatever works for you 👍 |
|
|
|
I just pushed https://github.com/KrauseFx/fastlane/releases/tag/1.29.1 which now will automatically detect the export type if you use |
|
Fastfile or Gymfile? before, Fastlane was able to infer that that profile was Enterprise and do the right thing. Where would I put that? |
|
@kdawgwilk woot! Do you mind pointing to the PR with the change? I'd like to check it out, and see if it's been fixed for me. |
|
I struggled with the "No applicable devices found" issue for a while.
(iOS 9.2, Xcode 7.2, OS 10.11.2) |
|
@KrauseFx still has this issue.. |
|
|
|
From 1.3.0, gym will output more information about the underlying failure. To everyone having this issue, including @skywinder, @JaviSoto @kcharwood, I suggest to try with the latest gym without use_legacy_build_api: true. If things still fail:
Report outputs for both attempts if it still fails. Let us know if step 2 fixes it for you. Thanks! |
|
Tried again with 1.3.0, failed with this error, plus a lot of output: Any idea how I would run that PR locally using RVM and Bundler? |
|
@kinwahlai I already pushed a new |
|
@kinwahlai cool |
|
This seems to have fixed the issue for me. Will this work on a Jenkins install as well? That's really my only concern moving forward. |
|
I actually run into the same issue right now. I tried the same export step with Xcode and the requests time out. Maybe this actually sends some kinds of requests to Apple to validate something? |
|
I just tried again without legacy API, I get this: |
|
@JaviSoto do you get more output after EXPORT FAILED ? Are you sure you are using gym 1.4.0 or later ? |
|
I'm using 1.5.2. This is all I see: |
|
@JaviSoto it cannot be 1.5.2. The latest release of gym is 1.4.0 and should display a different output. I suggest you try updating gym ( |
|
Oh, I'm sorry, that was my fastlane version, my gym version is indeed 1.4.0. And I don't see anything outputted besides that :( |
|
I'm using Before the output above, it fails to require sqlite3, even though I've already did install on the system ruby. |
|
Figured it out, I'm using |
|
Hit by this as the Root Apple WWDR cert has expired; try these: Open up Keychain Access. https://www.reddit.com/r/iOSProgramming/comments/45siza/this_certificate_has_an_invalid_issuer/ |
|
@bencollier That's already solved in the latest release. Regarding this issue I don't think In most cases the error are more related to the ruby & ruby gems setup of the machine, than anything else. |
|
This issue was migrated to fastlane/fastlane#3193. Please post all further comments there.
|
and others
I'm not sure what happened or at what
gymversion this broke in, but building for Enterprise distribution now fails when usinggymwithfastlane.I am also using
sighwithfastlaneand have code signing set up as recommend (using$(PROFILE_UDID)).Here is there relevant part of my my
Fastlanefile:Note everything works when building for App Store distribution. The only thing that changes for Enterprise distribution is the bundle identifier (
ENV["BUNDLE_IDENTIFIER"]) and the team ID (ENV["APPLE_TEAM_ID"]).As far as I can tell, all my certificates / provisioning profiles seem to be in order. The
sighstep runs successfully with the appropriate bundle identifier and I do have a valid Enterprise distribution certificate installed on my machine with its private key.Even though
gymdoes not complete, the archive is available in the Xcode Organizer and I can successfully export the IPA from the Organizer (Export > Save for Enterprise Deployment > Export one app for all compatible devices).Using
gym 0.6.2. Thanks @KrauseFx for all the hard work! :) I hope this isn't a dumb oversight on my part.The text was updated successfully, but these errors were encountered: