Slashdot Mirror

← Back to Stories (view on slashdot.org)

BlackBerry Code Signing Server Outage

Posted by Unknown on from the no-keys-for-you dept.

ThirdNormal writes "In a really painful move for most third party developers RIM's code signing servers have been down and having issues since the weekend started. This has caused a furor in the Blackberry Support Forum, and must surely exacerbate the defecting of developers from the Blackberry platform."

5 of 32 comments (clear)

  1. Re:A little bit late by zill · · Score: 4, Funny

    Great, I can't wait until the slashdot story tomorrow about the outage being resolved. The suspense is killing me.

  2. Re:When will they learn? by grub · · Score: 2


    Apple doesn't require access to their code signing servers to run an app-in-progress on development devices or the simulator.

    If this outage happened at Apple , it would have affected (only?) those uploading apps to the store.

    --
    Trolling is a art,
  3. What device on which to test? by tepples · · Score: 2

    Android development is free.

    Development includes testing, which requires buying hardware on which to test. The last time I checked, Android-powered devices on which to test software were by and large more expensive because they tended to be $500 cell phones rather than $250 media players. People recommend the Archos 43 Internet Tablet as an Android-powered alternative to the iPod touch 4, but it doesn't come with access to Android Market. People recommend the Samsung Galaxy Player, but it wasn't even available for me to buy when I checked last week.

  4. Re:Dihydrogen Monoxide by tepples · · Score: 2

    Code signing is a malware protection feature

    Sure, when your definition of "malware" includes everything developed by individuals working out of home offices. This is the case with, say, Nintendo.

  5. Blackberry juice by skjolber · · Score: 2

    I must say that although I like Blackberry, but other FAILS and now this really disappoints me. And my customers. When people create sites like this:

    http://isthesigningserverdown.com/beta/

    then something is seriously wrong.

    A short summery of the issue at hand: An application is divided into multiple files for over-the-air install. Each files is signed individually and might require signatures from more than one server, all depending on what APIs are in use. So at the moment I need 15-20 signatures per application per build, even a fairly low chance of an unserved request still makes the system fail as a whole. And if one type of server is down, 100% of builds fail.