09-29-2012 11:47 PM
Hmm. Well, I don't use FB, so unfortunately I can't pull it up and find out where that option lives these days. The knowledgebase article was from 2011 and I think FB Burrito was the current version at the time. Adobe may have moved that option. I suggest Googling for "Flash Builder 4.x change application deployment mode" and variations (where you replace "4.x" with whatever version you're on). Maybe the built in help files from Adobe have the info too; I don't know, since I haven't used FB for over a year.
09-30-2012 03:20 PM
09-30-2012 06:15 PM
09-30-2012 08:51 PM
Everytime you resign your app, it needs to have a different version number (you can just increment the build number if you wish).
10-02-2012 07:43 AM
10-09-2012 06:26 PM
So, I've fixed most of the issues and RIM tells me -debug is no longer appearing, however, my submission of a new release is being denied (File bundle (Countdown.bar) has been rejected. Package ID is required for all .bar file. If this is an upgrade, Package ID must match Package ID in original file bundle.)
this makes me think something went wrong with signing keys (I DID request new ones, but theyre in my inbox and haven't been downloaded)
but Flash Builder also refuses to run the app on the simulator, which makes me think it isn't the signing key at all.....
Deployment Failed: Info: Sending request: Install
Info: Action: Install
Info: File size: 7811337
Info: Installing ...
Info: Processing 7811337 bytes
result::failure 500 META-INF/MANIFEST.MF:22: unknown attribute 'Entry-Point-Key'
10-09-2012 06:33 PM
The error message "If this is an upgrade, Package ID must match Package ID in original file bundle" usually is in relation to signing keys. If your origonal keys are lost, you can ask for RIM to maually reset this for you in AppWorld.
10-09-2012 06:49 PM - edited 10-09-2012 07:00 PM
I have my original keys, but i am wary of unregistering because i'm eligible for a free playbook as long as this is not a new release, which is what would happen if i have to apply new keys
Also, i was just able to check my Package ID in my old release file and the new one, they match. Does this indicate this is an issue on RIM's end?
10-10-2012 11:30 AM
This error can also occur if your first BAR file was unsigned and you try to upload a signed version. To resolve it, explain the scenario to App World Vendor Support and they can reset that for you.