Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

bbwp builds debug bar file when -d is not present #83

MSohm opened this Issue Dec 19, 2011 · 4 comments


None yet
4 participants

MSohm commented Dec 19, 2011

BlackBerry WebWorks SDK for TabletOS

bbwp builds debug bar file when -d is not present

If you use the instructions documented here to create an unsigned application: https://bdsc.webapps.blackberry.com/html5/documentation/ww_developing/compile_ww_app_for_tablets_1873322_11.html

Package a unsigned application for tablets

The BlackBerry WebWorks Packager uses the BlackBerry WebWorks archive test.zip file to produce an unsigned version of the compiled application.

bbwp test.zip -o compiled

In the manifest Application-Development-Mode is set to true.

The prevents enterprise developers behind a proxy server from creating WebWorks applications because bbwp does not accept proxy parameters, which are required by barsigner to sign from behind a proxy server. They can be passed to blackberry-signer, however bbwp cannot be used to create an unsigned, non debug bar file that could be signed with blackberry-signer.

Steps to reproduce: Run: bbwp yourApp.zip.
Expected Results: An unsigned, non debug bar file is created.
Actual Results: An unsigned, debug bar file is created.

@ghost ghost assigned ababut Dec 20, 2011


dmateescu commented Jan 24, 2012

Bases on the bug's description, this issue is for BB WebWorks for Tablet (not for smartphone). Do we still need to address it ? It will require a BB WW for Tablet release.


MSohm commented Jan 24, 2012

Yes, this is for the Tablet release only. It needs to be addressed. Corporate developers still contact support about this issue.


kwallis commented Jan 24, 2012

I will move it to the correct repo.


kwallis commented Jan 24, 2012

Tracked now in the WebWorks-TabletOS repo:


@kwallis kwallis closed this Jan 24, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment