LiveCode Forums

I have read some previous post on this issue, but could not resolve my issue.

LC 9.0.5 RC 1

Has anyone had this issue lately?

see attachments.

Hello DR White,

This probably means that the provisioning profile you used to sign the app is not associated with any of the certificates stored in your KeyChain.

To fix this, create a new certificate, make sure you associate it with the provisioning profile (through the Apple Dev Centre), download the updated provisioning profile (which is now associated with the certificate you just created), and use this to sign the app.

Hope this helps.

Kind regards,
Panos
--

Panos,

I feel very sure you are RIGHT!

Yesterday I created a new certificate and provision, But they gave me the same error.
I believe that I am not associating something correctly.

Are there any lessons or simple instructions on how to do this. Everything was working fine, until my certificates expired.

Thanks,

David

I will say that I did something a little different yesterday and tried to create a Development profile with a wildcard.

Hello David,

See this lesson: http://lessons.livecode.com/m/4069/l/30 ... le-for-ios

BTW you have to put the exact app id (and not a wildcard) if your app uses some specific services, such as in app purchase, push notifications, HealthKit etc. Otherwise a wildcard is OK.

Hope this helps.
Panos
--

Panos,

Thanks for the link. I will try it when Apple resets my "Max Certificates".

David

Panos,

Thanks again for the link. That worked GREAT!!

I believe the thing that made the difference was in filling out the certificate request, in the past I don't think that the "common name" had to match the name in the application ID. This time I made the common name exactly like the name used in the application ID and everything was good.

Thanks,

David