01-26-2014 12:55 PM
01-26-2014 01:48 PM
01-26-2014 01:53 PM
01-26-2014 03:03 PM
01-26-2014 03:06 PM
01-28-2014 10:12 PM - edited 01-28-2014 10:13 PM
This is precisely why I refused to switch from my old keys to one based on my BBID. While I would be willing to let hired programmers (don't have any, yet) use my company owned key I wouldn't want to have to give them access to my personal signing key tied to my BBID.
I never really understood the wisdom of switching to BBID-based signing keys.
No. Once you change the signing key it is effectively a different app.
01-29-2014 12:02 AM
01-29-2014 12:34 AM
Actually, I know that about the upgrade path, but I do think I might have been mistaken about something. Do the signing keys still exist separately from the BBID? Can they be unlinked and reassigned to another BBID? If so, then yes, I did misunderstand. I was under the impression that the old signing key I used in the past would be replaced with a new one tied permanently to my BBID. I'm thinking now that is not correct. Correct?
@greenmr I think you've missed a beat here, linking the keys to your bb id isn't the same as signing with a new key.
You will not sacrifice the upgrade path in this case only if you create new keys as the OP was saying.
01-29-2014 12:40 AM - edited 01-29-2014 12:48 AM
Hm... not sure, I'll see what I can find out.
I'd made the assumption that the keys were just linked to the account and the acount was not used in the key generation however the fact that permissions are now being linked to the account may mean my assumption was wrong on this.
It also may explain a recent problem I had with an update to an Android app.
01-29-2014 01:03 AM - edited 01-29-2014 01:04 AM
Thinking about this logically I don't see how it can be as we would have heard thousands of developers screaming about their updates by now.
However there is still the possibility of a third step that binds that key to the bb id permanently so worth finding out if the bb id can be changed.