Could not locate device support files.

Question

Created Apr ’17

Replies 3

Boosts 0

Views 1.1k

Participants 3

After a couple years of not needing to update my apps, I've done an update and today tried to run it on a device. I received the message in the Subject, with the additional info, "This iPhone 6s is running iOS 10.3.1 (14E304), which may not be supported by this version of Xcode."

I'm developing on a pre-2010 Mac Pro, so I can't update to OS X 10.12 Sierra.

Because I can't upgrade to OS x 10.12, I can't upgrade to Xcode 8.3.

I assume that Xcode 8.3 has support for iOS 10.3, but I can't get there with this Mac Pro.

I fear that to update my apps to the latest iOS or release new apps, I'm going to have to buy a new Mac on which to develop. Is that true? Or is there another cause for this error that I can correct?

Answered by KMT in 226227022

True. New, or at least, newer, yes.

Also note that we are now being told to avoid Xcode 8.3 - move to 8.3.1 or higher. Xcode 8.3.2 is current as of today.

> I've done an update

Note that devs can still use minimum Xcode v6.x to submit to the store (restrictions apply), but what 'update' means in your example may obviate its use.

You had a good run w/that older mac. Time to move up and enjoy the full benefits that come with the adoption of a newer IDE.

Boost

Answer 1

KMT OP

Apr ’17

Accepted Answer

True. New, or at least, newer, yes.

Also note that we are now being told to avoid Xcode 8.3 - move to 8.3.1 or higher. Xcode 8.3.2 is current as of today.

> I've done an update

Note that devs can still use minimum Xcode v6.x to submit to the store (restrictions apply), but what 'update' means in your example may obviate its use.

You had a good run w/that older mac. Time to move up and enjoy the full benefits that come with the adoption of a newer IDE.

0

Answer 2

QuinceyMorris OP

Apr ’17

I don't think it's really practical to avoid buying a newer Mac for development. Apart from other considerations, staying with an older Xcode version means staying with an older SDK, which means your apps can't use newer APIs. The longer you hold out, the bigger that problem becomes.

In the short term, though, you can continue to debug your updates using whatever iOS simulator your current Xcode version has, and test on real devices via TestFlight. Unless you run into a problem you can't solve without running the debugger on the device, you should be able to QA your updates that way.

0

Answer 3

jzumsteg OP

Apr ’17

Thanks to both QuincyMorris and KMT for your answers. Not what I wanted to hear, but what I expected. Now I have to decide whether to continue or not; my apps would take a couple years to pay for an iMac or "newer" Mac Pro, and my current Mac Pro is just fine for everything else I do.

0