01-18-2012 10:27 AM
I have a question regarding signing keys validity.
I submitted an application to RIM AppWorld, which has been developed by my sub-contractor.
This subcontractor has a different signature files .(I can not install his signature files on my computer).
The question is about updating an application .. Let's say I have a new release (minor updates release),but this release is signed by my keys , not of my subcontractor keys ..
Can I submit this release as update of previously submitted application (signed by my subcontractor keys) or from RIM AppWorld perspective this update can only go as a New Application , because of my (new) keys ?
01-18-2012 11:28 AM
Update (Official Response from RIM) :
BlackBerry PlayBook application updates *must* be signed using the same keys used to sign the original application or it will be seen as a new application altogether and will be unable to be linked to the original.
For BlackBerry smartphone applications the signature applied to the application is not used to differentiate, so updates can be signed by any signature keys without issue.
Well,Google Android App Store standards are different :
Android is different :
certificate will need to be valid through at least October 22, 2033. Android Market
checks each application when uploaded to make sure it will be valid at least until then.
Because your updates must match what you used in the beginning, make sure you
safeguard your keystore file! If you lose it and you can’t re-create it, you won’t be able to
update your application, and you’ll have to issue a whole new application instead.