iOS standalone - what to do about code signing failures?

[Colin Holgate]

When you make a developer provisioning profile you are asked for the certificate to use. If you're making a distribution profile it should pick up on your current distribution certificate, but if you have changed that recently the provisioning profile won't be connected to the right certificate.

Something else to know, you can use wildcards in your app IDs, but LiveCode wants a full app ID. For example, you could make an app ID in the portal that is like this:

8263482.*

(the numbers are random, it would be whatever the system gave you). With that app ID you could create either of these apps:

rogerapp

com.rogerguay.rogerapp

Both ought to work, but LiveCode seems to like the fuller variation. An app ID of:

8263482.com.rogerguay.*

can work alongside these actual app IDs:

com.rogerguay.rogerfirstapp
com.rogerguay.rogerevenbettersecondapp

Now, that's all good for development purposes, but for distribution you want a full app ID that matches the actual product app ID, and is unique.

So, the right way to have a fresh start would be to make a new app ID that was the full ID:

com.rogerguay.rogerrealapp

make a new distribution ad hoc provisioning profile, that has all of your devices selected, used your current distribution certificate, and was based on that full app ID.

Once you have tested that build on your devices, and it's perfect, make another provisioning profile as App Store, and do one more build with the App Store profile selected. It's still based on the same app ID, and the distribution certificate, but it's anonymous as far as devices go. There is even a chance that you won't be able to test it.