Signature Check Failed

I know this is a newbie question, but...

I have not updated my watchApp for around three months till I tried today and get "Signature check failed. All app versions have to be signed with the same key pair."

The App ID is the same on the new file as the existing file.

I can see the id on the existing app in the App Store: Manifest AppID: 5351ff702e074b5f82bb2fcafd377add

and on the update it's:

<iq:application entry="main" id="5351ff702e074b5f82bb2fcafd377add". character for character the same.

I did upload a Beta version of the app with a slightly modified id for testing App Settings, but a) I have deleted the Beta version and b) I have restored the original id to the production version.

It feels like a caching issue so I rebooted my desktop and re-generated the export .ip file.

Any ideas?

Mac Monterey 12.5.1

VSCode 1.17.1

SDK 4.1.4

Top Replies

Alan.raceQs over 2 years ago in reply to FlowState +2 verified

FlowState said:
Since you appear to have different keys for different projects

Not intentionally I assure you. I only have one project!

I have found the location to edit, now to find why/how the developer…
FlowState over 2 years ago +1 suggested

It doesn't mean that the app ID is different.

It means that the private key you used to sign the latest version of the app is different from the private key that you used to sign the original version…
Alan.raceQs over 2 years ago in reply to FlowState +1

Hmmm, yes, thanks, and I have totally forgotten how to do that!

It's buried in MSC somewhere and I don't remember where.

All Replies

0 FlowState over 2 years ago

It doesn't mean that the app ID is different.

It means that the private key you used to sign the latest version of the app is different from the private key that you used to sign the original version of the app. (I think this has happened to you before.)

The only solution is to find the original private key and use that instead.

0 Alan.raceQs over 2 years ago in reply to FlowState

Hmmm, yes, thanks, and I have totally forgotten how to do that!

It's buried in MSC somewhere and I don't remember where.

0 FlowState over 2 years ago in reply to Alan.raceQs

CMD-SHIFT-P > User Settings > Monkey C > Developer Key Path

You can also override this setting on a per-workspace basis as follows:

CMD-SHIFT-P > Workspace Settings > Monkey C > Developer Key Path

Since you appear to have different keys for different projects, you might want to put the most frequently/latest used key in the User settings, and override the Workspace Settings for any project which uses the older key.

+1 Alan.raceQs over 2 years ago in reply to FlowState

FlowState said:
Since you appear to have different keys for different projects

Not intentionally I assure you. I only have one project!

I have found the location to edit, now to find why/how the developer key has changed. Thanks for the heads up.

0 FlowState over 2 years ago in reply to Alan.raceQs

No problem. Good luck finding your old key! You absolutely need that key in order to update your app. When you do find it, I suggest making secure backups in a couple of places (including cloud storage). You can encrypt the backups if you're worried about security; I personally use password-protected zip files for basic stuff like this.

0 Alan.raceQs over 2 years ago in reply to FlowState

My developer key was in the usual place, VSC/IQ had corrupted the location.

VSC was pointing to {home}/Downloads/developer_key which was dated July and quite different from my working key which is at {home}/developer_key.W10.

I have no idea where the corruption arose.

But many thanks for directing my attention away from the App ID.