11-27-2010 08:55 PM
I was testing the Export Released Build process to be then installed on the PB. The release build normally build the AIR installer file. What would be the best process to extract the non-debug version of an application (SWF, XML files, assets) to be sent to the PB like the debug version in /bin-debug normally does?
Solved! Go to Solution.
11-28-2010 08:58 AM
I am new to BB and Playbook development, so this may not make sense, but at this point I don't think the "Export Release Build" is useful for the Playbook. When you create a "Run Configuration", there are install options. Under the "Run Configurations", when you create a new configuration for the BlackBerry Tablet Air Application, the Deployment Method states "Target (IP Address of Host Name of the Device or Simulator).
My guess is that you use the run configuration and the IP address of the device to install applications to the physical device.
BTW, Adobe will probably have an option in FB 4.5 to create mobile apps, targeted at the Playbook. I think they currently have that for the Android, but plan to expand their supported mobile devices.
This is an Adobe pdf on Building Air apps. Chapter 11 has information on how the Android is supported.
11-28-2010 11:46 AM
12-01-2010 10:34 PM
Export Release Build is supported in FB 4.5 integration. Not in FB 4.0. I don't know if you can turn off debug in FB 4.0, if you can, you can just package application using same launch configuration but select Package Only and Production Mode.
12-02-2010 12:31 AM
Until the tooling works it out, one method is to create the .airi file in the export process. This .airi file is just a zipped up package, change it to .zip. And then follow the steps I posted on how to repackage AIR for Android .apk apps into .bar applications at the post here:
12-05-2010 12:22 AM
Totally spaced it on this one. In Project -> Properties -> Flex Compiler then in the "Additional compiler arguments" text field add "-debug=false". That will build non-debug SWF's, they still get put in the bin-debug folder.