03-05-2011 01:22 PM
I'm getting this error in the second last step of the signing process. I got an email saying I successfully registered with signing server RDK. Any ideas?
Solved! Go to Solution.
03-05-2011 01:26 PM
03-05-2011 01:29 PM
Also, if an error occurs in step1 of the signing due to an XML error, it will require you to increment your version because when you do it again, it will say that it is already registered.
If there is an error, why does signing record it in their database??? Pain.
03-05-2011 01:58 PM
Where do I find blackberry-tablet.xml? Should my -app.xml have author tags? I followed that link's intructions and still getting the error.
03-05-2011 02:01 PM - edited 03-05-2011 02:02 PM
You have to create it and save it in the same folder as the app.xml file; Here is a sample:
<qnx> <initialWindow> <systemChrome>none</systemChrome> <transparent>false</transparent> </initialWindow> <publisher>MY CN NAME HERE</publisher> <splashscreen>assets/splash.png</splashscreen> <category>core.utils</category> <icon> <image>assets/icon_86.png</image> </icon> </qnx>
Be certain that this file get included in the BAR file during the packaging command.
03-05-2011 02:21 PM
Thanks John. I included the blackberry-tablet.xml in my package but unfortunately it isn't helping the Package-Author in Manifest error.
03-05-2011 02:23 PM
I got his error when I tried taking a shortcut by signing a bar file that I used Flash Builder to create. For some reason, packaging the bar file with the command prompt instead of Flash Builder worked.
03-05-2011 02:30 PM
03-05-2011 02:30 PM
Does your blackberry-tablet.xml file have the same publisher listed as your-app.xml file under publisherID (if you have publisherID filled in)?
Do both of these match the name under your Certificate you got from RIM, which should also match your App World vendor account publisherID.
Follow the guide I linked to make sure you've set the -debug=false and then extract the created bar, ensure the manifest file is accurate, and then repackage via cmd.