CODEWITHSUNDEEP
iosiphonexcodeswift
Connor Hicks
Connor Hicks

Reputation: 775

XCode 6.3 Beta shows iOS 8.3b device as "ineligible"

I haven't used XCode since the first 6.x beta last summer. Today I installed the newest iOS beta on my iPhone 6 and the newest XCode beta from the developer portal. I created a new single-page swift application with an 8.3 target, and then tried to launch it on my device, but XCode shows it as ineligible in the build menu.

ineligible device

Any help on fixing this issue would be appreciated.

Upvotes: 16

Views: 10110

Answers (7)

Pavel Smejkal
Pavel Smejkal

Reputation: 3599

In my case, selecting the device from Product --> Destination worked great.

Upvotes: 109

joat
joat

Reputation: 71

You may need to login to the Apple Developer center and agree to the new terms of service. After that, do the following to update the provisioning profiles:

  1. Open Xcode
  2. Open Preferences...
  3. Select the Accounts tab
  4. Select your Apple ID
  5. Select View Details...
  6. Hit the refresh button in the bottom left corner

If you get an error about agreeing to the terms of service just wait a few minutes and try to refresh the provisioning profiles again.

Edit: For those still having trouble with ineligible devices, here's something else to try:

  1. Open Xcode
  2. Open Window
  3. Select Devices
  4. Control-click your device on the left side of the window and select Show Provisioning Profiles...
  5. Use - to remove all profiles (Xcode will install the necessary profile on the device when you launch the app). I had a bunch of old/extra profiles on my device.
  6. Double-check all settings in the Code Signing section in the build settings for your project and targets. Unfortunately I can't be more specific here but use your best judgement.

Upvotes: 7

SHS
SHS

Reputation: 1412

Edited:: 2015/Apr/27 Updated xcode version to 6.3.1 The problem was solved.

May be the update is required.

Upvotes: -1

Vaiden
Vaiden

Reputation: 16112

According to the changelog, Apple has fixed this in XCode 6.3.1 If this issue still bugs you, you might wanna upgrade your environment.

Upvotes: 0

Wookie
Wookie

Reputation: 812

Had this problem upon upgrading to the production version of Xcode 6.3. I tried all of the other solutions that were mentioned, and wasted hours trying various other things, but none of it worked. What did work was the nuclear option:

  • Uninstall Xcode

  • rm -rf "~/Library/MobileDevice/Provisioning Profiles/"

  • rm -rf "~/Library/Caches/com.apple.dt.Xcode/"

  • rm -rf "~/Library/Application Support/Xcode/"

  • rm -rf "~/Library/Developer/

  • Go revoke and delete your certificates and provisioning profiles in the iOS Developer Portal, then do the same in your Mac's key chain.

  • Install Xcode

  • Open Xcode, go to Preferences, add or select your iOS dev account, then refresh it to get new certificates and such (answer yes when prompted). Seems like you might also want to refresh it once again in some cases.

  • Update your project to point to those new credentials, where applicable

Upvotes: -1

kalpeshdeo
kalpeshdeo

Reputation: 1274

The fix is: Go to Product > Destination, and even though it says your device is ineligible, it will still allow you to select it, then building to it will work.

Upvotes: 8

matt
matt

Reputation: 534885

If you haven't done this since last summer, you probably need a complete new set of credentials. (This is because the entitlements for running a Swift app on a device changed.) Clear out everything and start from the bottom up with a new developer identity. Then create the development profile. Finally, attach the device and make sure to tap Trust and wait for the symbols to be copied over. You will then probably need to detach the device and attach it again, but at that point if you attempt to build and run on the device it should work.

Upvotes: 6

Related Questions