Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Adobe AIR Development

Reply
Contributor
Posts: 13
Registered: ‎08-08-2010
My Device: 9630
My Carrier: Verizon

Signing issue - file not found

Hello,

 

I followed the steps to sign and export/release an application here: http://docs.blackberry.com/en/developers/deliverables/23959/Configure_app_signing_Flash_Builder_1422...

but in the Packaging Settings Screen (with "Enable digital signing" checked), when I click on [Finish], I get the message:

"Error occurred while packaging the application

Packaging failed:1

Error: The system cannot find the path specified"

 

and I haven't been able to find a log or something that tells me which path is incorrect.

 

I'm building a simple app - 2 .png files and two views mxml files. I followed some advice saying that the <content> tag in the -app.xml file needs to be updated with the same name as the .swf file, but I'm at a loss here.

 

Thanks!

 

 

Contributor
Posts: 13
Registered: ‎08-08-2010
My Device: 9630
My Carrier: Verizon

Re: Signing issue - file not found

Just wanted to see if there are any updates here - I'm pulling my hair out Smiley Happy

That's for only a "Hello World" application, and I can't even build it! I'm running Win7, started FB Burrito as Administartor, playbook sdk 0.9.4. 

 

blackberry-tablet.xml:

 

<qnx>
  <initialWindow>
    <systemChrome>none</systemChrome>
    <transparent>true</transparent>
  </initialWindow>
  <publisher>XXXXXXXXXX</publisher>
  <category>core.internet</category>
  <icon>
   <image>blackberry-tablet-icon.png</image>
  </icon>
</qnx>
I'm really at a loss here.
Thanks!

 

Highlighted
Developer
Posts: 249
Registered: ‎11-02-2010
My Device: PlayBook
My Carrier: -

Re: Signing issue - file not found

I think you may try to export the release in a directory that does not exist.

If you're using the default "bin" directory, check that it exists before executing the Export (you have to manually create it actually)

 

 

JC