RIM Simplifies Requests for Replacement Code Signing Keys

Throwingpapersintheair

Back in August of last year I ran into the issue of having to replace my BlackBerry code signing keys. RIM does not document how to backup your code signing keys and move it between computers but there are ways to do that. On the other hand first time developers sadly usually learn this the hard way. Back in August I posted the instructions on how to email RIM developer support (devsupport@rim.com) for new code signing keys but RIM let us know that they have changed it up a bit.

Here is how they describe the new process:

Obtaining replacement BlackBerry code signing keys is today easier, faster and free of charge. RIM has simplified the process of obtaining replacement BlackBerry code signing keys to better serve its developer community. The process is now automated, fast and free of charge. If a developer is in need of replacement signature keys, they can simply make a request through BlackBerry.com/SignedKeys. The turnaround is fast and no administration fee is required.

In other words RIM is simply letting you place a request for a new set of signing keys instead of asking for a replacement. Not groundbreaking but I am hoping for the day when RIM automates it! If Chase can give you a ten thousand dollar credit decision within 30 seconds I am sure RIM can find a way to give you code signing keys in the same amount of time.

I asked that RIM update the code signing page to note the change in how to request code signing replacement keys. Hopefully they will tackle making the code signing process less “scratch your left ear with your right hand” and more a simple process. For example, you need to change the version number of a PlayBook app every time you sign it. Problem is it will only accept a certain format of version numbers which is not documented anywhere… Oh and then you need to pass along a –BuildID in the code signing command which does some other magic I have yet to figure out.

Anybody else want to help me create a list for RIM on how they could make the build process for BlackBerry smartphone and PlayBook apps more streamlined? Sound off in the comments!

6 total comments on this postSubmit your comment!
  1. Being able to resign PlayBook applications with the same version number would be nice. Under the current setup it isn’t really clear what happens when you recompile the same version number after you have already signed the app.

  2. is RIM getting simple ? back to basics

  3. I don’t think it’s working. We’ve been trying to get keys for a month and I filled that form out on the twelfth and have not received any keys and have been watching spam filter closely.

1 pingback on this post

Latest Articles from

AndroidEffect - Improving Android One Tip at a Time

BlackBerry© is a registered Trademark of BlackBerry Limited. BerryReview is in no way affiliated with BlackBerry Limited though sometimes their lawyers send us love letters...

Copyright © 2007-‘2014’ BerryReview LLC