Submitting to the #%^%#? App Store

[jonathandlynch at gmail.com]

Okay. - I got it submitted :)

I had revoked an older certificate to make sure I was using the right one, but that certificate was still in the key chain. 

Fingers crossed they like it on the first try.

Sorry for my hidden curse word there - it was just one of those moments.

J

Sent from my iPhone

> On Jul 4, 2017, at 11:01 PM, jonathandlynch at gmail.com wrote:
> 
> I created a new profile just for this - still get the same error.
> 
> After that I tried manually codesigning, but then I got the same error again.
> 
> Any other ideas? And thanks for taking the time on this - it is much appreciated.
> 
> J
> 
> Sent from my iPhone
> 
>> On Jul 4, 2017, at 10:35 PM, Colin Holgate via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> You choose a profile in Standalone Application Settings. There’s a danger of picking an old one. See discussions like this on how to remove out of date ones:
>> 
>> https://stackoverflow.com/questions/26732251/how-to-remove-provisioning-profiles-from-xcode
>> 
>> It should have a certificate associated with it, and unless you recently resubscribed it ought to work.
>> 
>>> On Jul 4, 2017, at 7:30 PM, Jonathan Lynch via use-livecode <use-livecode at lists.runrev.com> wrote:
>>> 
>>> Hi Colin,
>>> 
>>> Yes and yes 
>>> 
>>> Do we need to sign the actual file after it is created? I thought that happened when we created to executable from LC.
>>> 
>>> Sent from my iPhone
>>> 
>>>> On Jul 4, 2017, at 10:05 PM, Colin Holgate via use-livecode <use-livecode at lists.runrev.com> wrote:
>>>> 
>>>> Are you using an App Store Distribution profile? Was its certificate your Distribution one?
>>>> 
>>>> 
>>>>> On Jul 4, 2017, at 7:02 PM, Jonathan Lynch via use-livecode <use-livecode at lists.runrev.com> wrote:
>>>>> 
>>>>> Both venting and seeking advice.
>>>>> 
>>>>> Actually submitting an app to iTunes Connect is not easy, to put it mildly.
>>>>> 
>>>>> I am getting an error...
>>>>> 
>>>>> The executable 'Payload/Augmented Earth.app/Augmented Earth' must be signed with the certificate that is contained in the provisioning profile.
>>>>> 
>>>>> I have no idea how it could be wrong. The distribution provisioning profile seems correct to me. Is there a step I am missing? I thought I was following the steps outlined on the LC site.
>>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at 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 at 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 at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode