I have Internet

If you check around the playbook tablet os support forums you will see a lot of commotion about how to sign your playbook application.In most cases signing with Flash Builder ( Burrito in my instance) gives you a false impression of your application being signed. To verify that your application has been signed one would need to open the created .bar file with some type of archiving application (winrar,7zip etc). In the META-INF folder you should have a total of 5 files.

MANIFEST.MF
AUTHOR.EC
AUTHOR.SF
RDK.EC
RDK.SF

If you don’t have these files then someone went wrong. You can of course do this via command line as found here HOWTO: Sign your Applications from CMD, but this is not an optimal workflow for myself. After testing I found that the signing usually fails in the following cases.

1. You forgot to input a value for , in your -app.xml file. The fact that it clearly states that this node is optional in one big fat lie. This MUST be populate. The value to be populated here is your company/author name that you used when setting up your vendor account.

2. Version number is in an incorrect format. Now this one was a random find. It seems that the version number has to have 3 parts, which the comment about doesn’t say this is a requirement but I needed to have this to sign my application . So something like 1.2 would fail, while 1.2.0 would produce an .bar with all the files I mentioned above.

3. You may only sign your application once per versionNumber, I guess this makes sense, I would be nice that this would automatic increment on each sign. To fix this just add an 0.0.1 for each version until you meet your next minor/major release. It doesn’t help that the vendor portal doesn’t allow for this notation and only in . format. Maybe this will change with time

Hopefully this helps others out there.