A short question about Xcode
waprothero at gmail.com
Fri Apr 17 11:35:55 EDT 2020
I’ve been where you are, with the maze of requirements to get an app on iPhone. One thing I found was that the trail of mis-steps left a confusing mess of invalid entries in the keychain and Xcode app, and in the other places in my . When I got rid of every entry that I had made and started over from scratch, I had success finally. So, every time I get to that point in the project, I do a housecleaning, then religiously followed the steps some of the livecode app gurus have posted. I’m fortunate in that I only need to use my app on my own iPhone and don’t have to go thru the apple store.
FYI— Sorry that I didn’t note the author of this snippet, but I found it very useful and stored it in my notes. It may not be the most current, as well.
Ah yes - one of the biggest GOTCHA’s there is when working on Apple certification…
I’ve found the best approach is to keep my dev machine scrupulously clean as regards old certificates, and a session with Keychain Access pays dividends.
The same thing goes as regards old provisioning profiles - you should find all provisioning profiles on your mac stored at '/Users/<userName./Library/MobileDevice/Provisioning Profiles’. Regular cleaning out of that folder and then using Xcode to pull down fresh copies is the way to go
In general ‘good hygiene’ with your certificates and profiles is necessary and will prevent much head thumping, cursing, gnashing of teeth and tears at bedtime :)
And finally, I’ve found it best to keep old copies of Xcode on my machine in their own sub-folder (individually named) in the Applications folder whilst keeping the executable named “Xcode.app”
—End of snippet
William A. Prothero
> On Apr 16, 2020, at 2:57 PM, scott--- via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hello Graham,
> When you created the development provisioning profile, I assume you added your iPhone’s UUID to the list of allowed test devices. In the Standalone Application Settings—> iOS—> Basic Settings (tab) did you select the correct profile. (Simulator doesn’t care about profiles but your real devices need to be specifically allowed.) If you just added one, be sure to restart LC so that it sill see it.
> Scott Morrow
>> On Apr 16, 2020, at 1:20 PM, Graham Samuel via use-livecode <use-livecode at lists.runrev.com> wrote:
>> Ralph, I am using a development provisioning profile for iPhone. It was created this month and expires next year. I will try to go over the whole process again. I did as much as I could to include all the icons and splash pages needed for all the phones I was likely to encounter (that was about 5 different types). Do I have to include ones that nobody is going to use?
>>> On 16 Apr 2020, at 22:04, Ralph DiMola via use-livecode <use-livecode at lists.runrev.com> wrote:
>>> You can ignore the "this version of Xcode (10.1) was not compatible with the iOS 13 on my iPhone XS"
>>> Make sure your using a development provisioning profile. Create a new one and try using it. If I remember correctly I've also seen this when not all Icons or Splash pages are included.
>>> Ralph DiMola
>>> IT Director
>>> Evergreen Information Services
>>> rdimola at evergreeninfo.net
>>> -----Original Message-----
>>> From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Graham Samuel via use-livecode
>>> Sent: Thursday, April 16, 2020 3:05 PM
>>> To: How to use LiveCode
>>> Cc: Graham Samuel
>>> Subject: Re: A short question about Xcode
>>> Sadly, my test targets are just simulators. No real device is mentioned.
>>> However, following Ralph’s advice (thanks), i reconnected with my phone unlocked. Things looked promising, but then a message came up saying that maybe this version of Xcode (10.1) was not compatible with the iOS 13 on my iPhone XS, which is my main test device (it’s OK in the simulator). It then tried to do the loading of the app into the phone and eventually said
>>>> The entitlements specified in your application’s Code Signing Entitlements file are invalid, not permitted, or do not match those specified in your provisioning profile. (0xE8008016).
>>> I suppose that may be the end of that. I need a new iMac - the one I’ve got won’t run a later version of Xcode. Sadly they are rather expensive. I can’t visit anyone else’s, even if I could find one, since i’m in lockdown.
>>> Nothing, but nothing, is simple when trying to deploy to iOS.
>>> [Sound of grinding teethe]
>>>> On 16 Apr 2020, at 20:22, scott--- via use-livecode <use-livecode at lists.runrev.com> wrote:
>>>> I can’t recall whether this is specific to a particular LC license but when physically attaching a device to the computer, on my setup that mobile device appears under the menu Development —> Test Target (along with simulator options) and can simply be selected as the test device… which saves the added step of dragging into Xcode.
>>>> Scott Morrow
>>>> Elementary Software
>>>> (Now with 20% less chalk dust!)
>>>> web https://elementarysoftware.com/
>>>> email scott at elementarysoftware.com
>>>> booth 1-800-615-0867
>>>>> On Apr 16, 2020, at 10:11 AM, Graham Samuel via use-livecode <use-livecode at lists.runrev.com> wrote:
>>>>> I’m following the LC lesson 'How do I build an iOS application?’. I think I’ve done everything they mention, and I have my Apple developer credentials and three iOS devices registered. I have saved my iOS app as a standalone. But when I get to this instruction about getting my app on a real device:
>>>>>> 1) Open Xcode
>>>>>> 2) In the 'Window' menu select "Devices"
>>>>>> 4) Select your connected iOS device
>>>>>> 5) Drag standalone app to "Installed Apps" section of device window
>>>>>> Your app should now be on your device
>>>>> There is nothing in the Devices section for me to select (plenty of stuff in the Simulators, but so what?). Do I have to fiddle with keychain or particular folders or what? I have no idea what to do next (not for the first time!).
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode