Graham,
I can take some notes. What I did to fix it was to delete all my developer 
certificates from my keychain and re-activate them. That was after I realized 
that the reference to "identity" actually meant that it couldn't find a valid 
certificate. Now it seems obvious, but didn't at first. I remember some 
postings a while back re the need to get a new certificate. In the process, I 
mucked up my entire keychain and had to recover it using the wonderful "Time 
Machine". 

Now I'm fiddling with the provisioning profile to make its setup match with the 
standalone settings for iOS. One thing I see as I fiddle, is multiple 
provisioning profile in the drop down menu on iOS settings. Each new change and 
download on the Apple dev site creates a new one and the name doesn't change 
unless I do in in the apple developer website. Haven't figured out a way to 
delete old ones yet, but that will come.

I'm just giving these details of my thought so that if somebody decides to 
write up this, with all it's messiness, they might see what newbies go thru. 
I'm not a newby anymore, but I only work with iOS occasionally and the process 
seems to always be painful.

I'll take some notes and if they seem relevant, I'll post them somewhere.

Best,
Bill

William Prothero
http://es.earthednet.org

> On Mar 23, 2016, at 2:46 AM, Graham Samuel <livf...@mac.com> wrote:
> 
> Care to write it up, William? 
> 
> AFAICS, coding in LiveCode is a trouble-free activity compared to deployment 
> on iOS (or indeed on LiveCode Server, Android etc). Arcane rules, 
> certificates, permissions… even the vocabulary seems to have been re-invented 
> to confuse the honest programmer. Of course, that’s just my view, and I am 
> not young. Still, it seems to me that one of the biggest challenges for 
> LiveCode is to make the whole process, from having the idea for the app all 
> the way to successfully publishing it, a journey with no u-turns, dead ends, 
> or deep frustration at lack of progress.
> 
> Just my two eurocents
> 
> Graham
> 
>> On 23 Mar 2016, at 04:34, William Prothero <proth...@earthednet.org> wrote:
>> 
>> Never mind…… Got it to work.
>> Bill
>> 
>>> On Mar 22, 2016, at 8:17 PM, William Prothero <proth...@earthednet.org> 
>>> wrote:
>>> 
>>> I can see, after Googling around a bit, that getting the certificates 
>>> signed and set up correctly is quite complicated, with lots of ways of 
>>> going wrong. With out-dated certificates, old provisioning profiles, etc.
>>> 
>>> I wonder if there is a way to make this more robust and transparent. Like 
>>> some app that will go through the settings, certificates, and provisioning 
>>> profiles and give a diagnostic. Or perhaps, could the Livecode diagnostics 
>>> give more information to help figure out what’s going wrong? This seems 
>>> like a real need to me.
>>> 
>>> Maybe it’s too much to hope for. It takes me a day or two of hair-pulling 
>>> to get this set up after being away from making iOS apps for awhile. 
>>> 
>>> Best,
>>> Bill
>>> 
>>>> On Mar 22, 2016, at 7:29 PM, William Prothero <proth...@earthednet.org> 
>>>> wrote:
>>>> 
>>>> I’m getting an error when I try to build an iOS standalone. It is:
>>>> “Could not find a valid identity to use with the selected iOS profile.”
>>>> 
>>>> Where should I look? I’ve downloaded a certificate and set the bundle  of 
>>>> the provisioning profile to org.earthednet.wWaterDetective, and it shows 
>>>> up in the Profile setting, and I set the internal App ID to 
>>>> org.earthednet.wWaterDetective.
>>>> 
>>>> I’m in LC 8 DP 16, using Xcode 6.2.1. 
>>>> 
>>>> Very frustrating. It would be really wonderful if, sometime, there was a 
>>>> list of possible complaints the standalone builder would make, with 
>>>> possible solutions, or at least some diagnostic things one could do.
>>>> 
>>>> Any suggestions would be much appreciated.
>>>> 
>>>> Best,
>>>> Bill
>>>> 
>>>> William Prothero, Ph.D.
>>>> University of California, Santa Barbara, Emeritus
>>>> proth...@earthednet.org
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode@lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your 
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to