New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export Failed with Xcode 7 - No applicable devices found
#3184
Comments
I assume this is an Ad Hoc profile? If you can't get it to work, you could try using the |
Indeed Ad Hoc. def fabricAndNotify(notifications)
sigh(adhoc: true)
ENV["PROFILE_UDID"] = lane_context[SharedValues::SIGH_UDID]
gym(scheme: "MyProj AdHoc", sdk: "iphoneos9.0")
crashlytics(notifications: notifications)
end |
gym(scheme: "MyProj AdHoc", sdk: "iphoneos9.0", use_legacy_build_api: true) |
Great, using the Do you know what causes it to fail when not using the legacy? I'll pay attention in the new releases, to know when to remove it. |
Sorry, I don't know why - somehow it seems to verify the devices in your Ad Hoc profile... |
Try performing:
|
I had the same issue occurring with a development profile just recently. I think this has to do with devices being connected to the machine. As it works fine on my laptop, but not on our CI server that has a bunch of iOS devices connected. |
|
Ok interesting enough I use Bundler with fast lane. I added CFPropertyList and sqlite3 to my gem file and it instantly started working. My guess is the way fast lane works with bundler may be the issue. |
I found that the problem was caused because of how Much as I tried, the only solution I have so far it to run |
use_legacy_build_api: true This worked for me, but wondering what side effects this will have if any. |
I am using gym 1.1.6(also gym 1.0.0)
|
Thanks for that response. I actually had a different error which I solved with use_legacy_build_api, but not sure I like that solution. So I tried your suggestion of 'gem install CFPropertyList' and 'gem install sqlite3' anyway for giggles. With or without the 2 gem install commands, I use use_legacy_build_api, and TA DA! fastlane/gym is successful! Again, not sure what ramifications of using the legacy api would be, versus new one. If someone could elaborate as well as provide some clues for a fix (are we still waiting on Apple?) that would help. I have taken caution to de-identify the company I work for. It took me a while to do this de-identification, hopefully it is going to help others as well. Error is here: |
@bassrock I added those two gems to my Gemfile and it resolved it for me as well. |
One more note for @bassrock 's solution: in our case it wasn't enough to just add the two gem to the We did a couple of additional tests and it seems that (at least in our case) the issue only happens if we have a Just in case someone would find this issue when searching for the error message ;) |
@viktorbenei Thanks for sharing that info, it'll help other developers! 👍 |
Hey everyone, we just pushed a new gym release with gym 1.11.1, that should fix an error in Let us know if that fixes the issue for you. If it doesn't work still, please share the complete output with the latest version of gym so we can further investigate the problem 👍 Thanks everybody for helping resolve this issue 🚀 |
@vegidio-symbio Thanks for following up. Can you share your full output for the lane you run when you get this error? Thanks! |
@KrauseFx after updating fastlane to the latest version and removing legacy_api call i am getting this error ```[14:36:38]: ▸ Signing DerivedData/MyApp/Build/Intermediates/ArchiveIntermediates/MyApp\ Beta/InstallationBuildProductsLocation/Applications/MyApp-Enterprise.app
Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}``` no idea how to fix it really, i substitute it the real app name for privacy fastlane version |
I think it is trying to apply bitcode app thinning even though it's an app build for enterprise. It is trying to apply the bitcode thinning to a set of devices which it is not finding. That is my theory. So for now, I am checking the build environement and if it matches and adhoc/entreprise type I use the legacy flag, if not I use the bitcode flag. |
Definitely not. All the bitcode is disabled everywhere. |
I am also setting the 'include_bitcode' to false, but I have the same error message as you pointing us to the fact that it is trying to 'thin' the app. => 'Step failed: <IDEDistributionThinningStep' |
As far as I remember 'include_bitcode' is false by default. Will check if that has changed recently. We don't have any extensions. |
Well I'm out of ideas… |
yeah i will keep debugging it, want to get rid of the legacy as well. |
Got exactly same error as well. |
@sbandol Are you sure you had the same error mentioning IDEDistributionThinningStep while trying to build for enterprise? |
@AppsTitude |
It looks like the same error indeed. I'll try setting the UIDeviceFamily. Thank you! |
Setting UIDeviceFamily did not work for me nor did set fastlane version to 2.2.0. I guess I'll use the legacy method for now (for non bitcode enabled build config) |
@sbandol Oh my god you were right! It was a lib (Instabug) which was missing its UIDeviceFamily info in its plist… Wow. |
interesting will try to update cocoa pod to set |
i have tried adding |
You are not the one needing to add UIDeviceFamiy. It is the lib's responsibility. So just update Instabug and it should work. If it doesn't maybe another lib is creating the same issue. |
I added to lib to verify if that's the case for our failure
…--
Sent from an iPhone
On Jan 11, 2017, at 00:49, Louis Encontre ***@***.***> wrote:
You are not the one needing to add UIDeviceFamiy. It is the lib's responsibility.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Same problem here. Using fastlane 2.7.0.
Using this in my Fastfile:
When setting Have no idea what I could try anymore... |
Little update here. Finally i digged into the log dir
That told me it has something to do with bitcode enabled. After I diabled bitcode in my project and changed my gym action to this:
it worked smoothly... Of course ... it would be nice to have bitcode enabled. But I think as long as Apple does not make it mandatory we will always struggle with this ... because so much tools and frameworks out there do not support bitcode right. In my specific case I think it's somehow the combination with carthage, which also still have some bitcode support issues. |
@orschaef I see the same kind of error message from |
Hi,
It works fine with Xcode 7 |
@saraht129 I was seeing this same problem, but disabling bitcode in gym didn't solve the problem for me. I had to go into my target's Build Settings and disable bitcode from there. After that, everything worked fine |
I had the same problem |
I just experienced the same problem with Xcode 8.3.1. However, none of the above suggestions worked for me. Turned out that Xcode 8.3.2 just released and that fixed the problem for me |
Hey Felix! I'm trying to export a lane that in previous Fastlane worked. I'm running fastlane v. 1.29.1 and gym 0.8.1.
I receive the following error:
Archive succeeds, but the export fails. I took a look here fastlane-old/gym#89 and here fastlane-old/gym#90 and tried some suggestions there, with no success.
Before updating from 1.28 to 1.29.1, I was having provisioning profile errors, and now this one.
Any ideas of what is causing this?
Thanks!
The text was updated successfully, but these errors were encountered: