-
Notifications
You must be signed in to change notification settings - Fork 54
Export Failed with Xcode 7 - No applicable devices found
#104
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: |
For the record, that one is also linked to #168. |
@bassrock I added those two gems to my Gemfile and it resolved it for me as well. |
This issue was migrated to fastlane/fastlane#3184. Please post all further comments there.
|
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 #89 and here #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: