I could not reproduce your release builds issue on 3.3.1-0.4.2. Could you please file a JIRA with specifics?
On Wed, Feb 19, 2014 at 8:21 AM, Bryan Higgins <[email protected]>wrote: > Hi Don, > > CLI 3.3.1-0.4.2 changed the run command so that "--device" is no longer > passed down to the platform scripts. BB10 relied upon this to start device > detection. I did not notice any communication about this on the list. > Perhaps the implementor didn't know enough about bb10 to know this would be > a problem. > > For 3.4, I've updated cordova-blackberry to make this the default > behaviour. In 3.3.1-0.4.2, you can work around by passing in "--device". > > I'll look into the issue you're seeing with release builds. > > Thanks, > Bryan > > > On Tue, Feb 18, 2014 at 8:10 PM, Don Coleman <[email protected]>wrote: > >> It looks like 3.3.1-0.4.2 has more problems >> >> * release builds don't get the version number from config.xml >> * release builds don't get use the launch icon from config.xml >> >> Is anyone using 3.4 with BB10? >> >> >> On Tue, Feb 18, 2014 at 6:02 PM, Don Coleman <[email protected]> >> wrote: >> >> > Cordova 3.3.1-0.4.2 can't find an deploy to locally attached devices. >> > >> > $ cordova run blackberry10 --devicepass ffffff >> > >> > Generating config.xml from defaults for platform "blackberry10" >> > >> > Preparing blackberry10 project >> > >> > Running app on platform "blackberry10" via command >> > "/Users/.../platforms/blackberry10/cordova/run" --devicepass 19034 >> > >> > Error: An error occurred while running the blackberry10 project.No >> > target exists, to add that target please run: target add <name> <ip> >> [-t | >> > --type <device | simulator>] [-p <password>] [--pin <devicepin>] >> > >> > Windows 7 with 3.3.1-0.4.2 does the same thing. >> > >> > Downgrading back to 3.3.1-0.1.2 fixes the problem on OS X >> > I'm hoping this is a bug and not intentional behavior? (Not a fan of >> > target add) >> > >> > >
