You're getting this when you try to upload to the store, correct?
Sounds like you're trying to use a different signing key than you used before. Once something is in the store with your key, you have to keep using the same key to update it - it's how the store checks the update is from the same person as the developer that submitted it.
If you no longer have the original key, maybe Garmin can do something on Monday.
Once you have a developer key, you want to keep keep it in a safe place and not change it. It's your key to the store for updates.
I'm just a part time dev trying to help Garmin and all I seem to come across each time I try and help sell there gear is problems.
Sorry. But there it is.
Some point back I was forced to create a new identity key, despite beinga dev from back in the early days. Been using that new key until a recent break only to find out for some reason it's now no longer valid and have to ask "Garmin" for a new one. Who/where/how do I ask Garmin?
Also why do I also see my apps download etc stats being constantly reset when they get to 20k or so?
Garmin i am seriously running out of patience with you, I suspect you are just trying to kill my watch face!
The whole developer key and signing thing first started with 2.1.0. So if you uploaded something with 2.1.1 or greater (you couldn't upload with 2.1.0 as it was a beta), that set your public developer key in the store for your app, so it's really only been in the last few months.
So it looks like you changed your key sometime between 2.1.1 and today. When you upgraded your SDK, did you do a "generate new key" or just browse for your old key? (you wanted to do a "browse" and use the old key), or maybe did you move machines and generate a new key?
Notice I said your "public developer key" in the store. Not even Garmin can tell you what your private developer key was. You can see if Garmin can reset your app to a "no key" state.
I keep my original developer key on a "cloud drive", so I can access it if I change machines, etc, and it's always off site and safe in the event of a HW failure, etc. If you lose your key, it can be a pain as you see - maybe removing your app from the store and submitting it as "new" in the worst case... See what Garmin folks say on monday...
A while back there was an issue with the Manifest ID where garmin sent out some new ones, but that's different than the app signing key.
I'm sorry that you are having continued issues. In regards to the issues with the older version of eclipse, we had to make certain changes to support the current versions. This caused issues with anything older than Eclipse mars. We have since updated our documentation to note the change. When it comes to app signing, the information posted by the other developers in this thread is accurate. Unfortunately, since it is a private key that is owned by you, we do not have the ability to retrieve it. It is good practice to save this in a secure place in the event of a hardware failure or any other unforeseen circumstance. The choice to begin using app signing is to protect the developer, Garmin, and the end user from any security issues or bad players with malicious intent. I apologize that it has been inconvenient and hope for the best in tracking down the missing developer key.
