BarSigner 500 unsigned error

Currently with the PlayBook 1.0.1 AIR SDK the error reporting for signing and debug token issues can be far too generic. The biggest culprit of this is the BarSigner 500 unsigned error. The team is actively working on returning more specific error messages for all the various use cases. In the meantime here is a list of the reasons why this error would occur. Hopefully this will help you debug the issue faster when you see this error.

  • There is no debug token on the device.
  • The debug token on the device has expired.
  • The debug token author does not match the author of the application being deployed.
  • The debug token author id does not match the author id of the application being deployed.
Continue reading » · Written on: 04-26-11 · 1 Comment »

One Response to “BarSigner 500 unsigned error”

  1. jacob Bullock wrote:

    I have been dealing with some serious issues tonight with debugging on the playbook. My problem turned out to be that when i copied the author id from the debug token details and pasted them into the blackberry-tablet.xml it was actually copying in special characters that looked fine in FB and in text mate. wasn’t until i opened the xml file in text edit that I realized it. So anyone who has checked all of the above items here, may want to take a look and see if they have special characters for the author or authorId values. Haven’t seen that mentioned on any of the forums out there.

    August 2nd, 2011 at 1:10 am

Leave a Reply