Could not find plist template for device target

[strongbow]

Yep, have XCode 6.2 installed as well as a bunch of previous ones.
cheers!

[dave.kilroy]

OK - and how are you managing the different Xcode versions?

Do you have each one in it's own individually named folder (leaving the app name untouched)? If not then sometimes LiveCode will get confused about which version of Xcode to use during build. If you think this might be happening to you (i.e. each of your Xcode apps are called something like "Xcode62.app" and are all in the Applications folder) and want to fix it, it would be best to uninstall all copies of Xcode except for one (probably the most recent one your system can use) and keep that one in Applications. Temporarily put it into a sub-directory and then install the other versions of Xcode you want, and when the installation completes move the version you just installed into it's own sub-directory - and repeat for each version you want. Then at the end move the version of Xcode you use the most back into the Applications folder and check LiveCode is pointing to the CORRECT version of Xcode, Phew!

Good luck, Dave

[dave.kilroy]

Just remembered, Panos once posted the following instructions to a user that was having an issue with Xcode (I haven't had to use this myself, but if you're comfortable with the command line doing it this way would be quicker than uninstalling and reinstalling lots of software...)

MANAGING DIFFERENT XCODE VERSIONS AT THE SAME TIME
It seems that the path is not updated and keeps the old path/to/Xcode_71.




IF DESIRED XCODE IS JUST IN APPLICATIONS FOLDER

1. Type in the OS X terminal:

sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

This command will update correctly the path for the active developer directory.

2. Make sure you have selected /Applications/Xcode.app under LiveCode -> Preferences -> Mobile Support



FOR VERSIONS OF XCODE IN DIFFERENT SUB FOLDERS OF THE APPLICATIONS FOLDER

I have a folder named "Xcode", which has subfolders named "Xcode_7_1_1", "Xcode_7_1", "Xcode_6_4" and a lot more. In each of these subfolders I have just Xcode.app. In other words, I avoid to rename the .app file, and I have just put each Xcode version into a different folder.

When I add a new Xcode version, I set this as the system default using
sudo xcode-select -switch /path/to/this/xcode/version


———

1. Open a terminal in the machine that fails
2. type: xcode-select -p
3. If the output of this command does not show that path to Xcode 7.2.1, change it
4. You can change it by typing the following command in the terminal:
sudo xcode-select -switch /full_path_to_Xcode7.2.1/Xcode.app/Contents/Developer
5. (type your password)
6. Type again xcode-select -p (just to make sure that now the OS uses the correct version of Xcode to do the codesign) - You should now be able to successfully create an iOS standalone.

———

/Applications/Xcode.app/Contents/Developer
/Applications/Xcode-71/Xcode.app/Contents/Developer

sudo xcode-select -switch /Applications/Xcode-71/Xcode.app/Contents/Developer
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

[strongbow]

Thanks for the tips Dave, particularly the info from Panos, but they're all in their own sub-folders and I've had no problems over many years of building apps. XCode 6.2 appears as the result of the command xcode-select -p so that would seem fine. Or ?

cheers!

[dave.kilroy]

Yes that all sounds in order :[

For building for earlier versions of iOS the only other straw I can think to grasp is: make sure your provisioning profile doesn't include anything that wasn't included in those earlier versions of iOS

If that doesn't work and nobody else can help then my advice is to give away your mac, sell your house, move to another country, change your name, buy a new mac, install LiveCode and try to build again

Oh and you should probably make offerings to any gods you follow...

Kind regards

Dave

[strongbow]

heheh, will try all of the above... including making offerings - by going on a March for Science on Earth Day tomorrow!
cheers!

[dave.kilroy]

Excellent! That could well do the trick

[LiveCode_Panos]

Hi all,

Due to changes in Xcode 8 and iOS 10.0, we are no longer able to support deploying iOS device standalones built with the iOS 8.2 SDK (i.e. the one that is included in Xcode 6.2). Unfortunately there is literally no way around this; Apple have changed the details of how some critical build tools work, and there's nothing we can do about it.

Starting from LiveCode **8.1.1-rc-1**, therefore, you can only deploy to iOS **device** if the standalone is built with the iOS 9.2+ SDK (i.e. the one that is included in Xcode 7.2+)

Note that this practically affects you only if you are on OSX 10.9.x, since the latest supported Xcode version on OSX 10.9 is Xcode 6.2 (and includes the iOS 8.2 SDK).

So to conclude, if you are on OS X 10.9 and you want to build iOS standalones **for devices**, you will have to either:

(1) upgrade to a newer OS X version (this is free) and use LC > 8.1.0 OR
(2) use LC 8.1.0 and Xcode 6.2

I would definitely recommend (1).

Best,
Panos
--

[dave.kilroy]

Thanks for the info Panos!

[strongbow]

Yes, thanks Panos for the comprehensive info!
cheers!