07-12-2011 10:27 AM
This issue continues today. Teams have been working around the clock but we do not have a resolution at this time.
We understand the impact this has on everyone developing for BlackBerry. This is being treated as an ultra high priority issue.
I don't have anything further to share at this point... but will try and find out what more I can reveal.
These sniper kittens are persistent. ![]()
07-12-2011 10:47 AM
Esto ya es mucho tiempo, el impacto mundial es inmenso! Lo peor es que nuestros clientes solo nos exigen... ellos no comprenden este problema y solo piensan en dinero... espero que se solucione pronto! vamos RIM
Saludos desde Acapulco, Mexico.
![]()
07-12-2011 10:53 AM
Did you reboot three times?
07-12-2011 10:57 AM
07-12-2011 11:22 AM
This is a work stoppage.
I know there has been some emotion in here.. but in all seriousness, are there no backups of this server? Is there not a secondary signing server for emergencies like this?
I think the saddest part of this is that we have had to rely on the external signing server site for accurate information.
07-12-2011 11:32 AM - edited 07-12-2011 11:34 AM
@Digbads:
Keep an email on the Twitter feed at http://twitter.com/#!/signingserver I'm sure i'll be posted on there as soon as things are working again. There is also the fantastic http://isthesigningserverdown.com/beta/ site.
07-12-2011 11:36 AM
Did you guys do a battery pull?
07-12-2011 11:39 AM
Blackberry developers fixing the signing server.
07-12-2011 11:40 AM
@MSohm,
I'm glad you can make light of the situation because I can't. I hope there is an open forum that we can voice our opinions during DevCon Americas.
07-12-2011 11:44 AM
After all this BS, including the fact that we still don't have an email client on the PlayBook (nor will RIM allow developers to publish mail or IM clients), I've completely lost interest in going to DevCon. It's more like, us DEVs are getting CONned.