There is no consensus on this.
See https://issues.apache.org/jira/browse/CB-8730. I will venture for
now that this bug is valid, because it broke the existing pre-3.7.0
behaviour, and the fix to make it build for emulator only was
unintended.
On Wed, Mar 4, 2015 at 7:20 AM, Michal Mocny
I think its fine to fail if the attached device isn't provisioned. Perhaps
we could append a message explaining `cordova run --emulator` or `cordova
emulate` commands, but I think even that is not necessary.
My personal expectation is that once I plug in a device using a cable, I
very likely
What is the expected behaviour here?
`cordova build`
My expectation is that it would build for both device and emulator. In
iOS pre-3.8.0 it does, but now it only builds for emulator only after
the node.js script port, which may or may not be a bug depending on
consensus.
The online docs and cli
...@gmail.com]
Sent: Tuesday, March 3, 2015 3:09 PM
To: dev@cordova.apache.org
Subject: Re: [CLI] Default target when not specified for build, compile?
Defaulting to device might be problematic on iOS: sure we can detect if a
device is attached (using iso-deploy), but the build might fail because
Imho, it should do what: cordova run would do.
I would think it would run once for each platform, defaulting to device if
attached.
On Tue, Mar 3, 2015 at 4:37 PM, Shazron shaz...@gmail.com wrote:
What is the expected behaviour here?
`cordova build`
My expectation is that it would build for
/build/device/bb10app.bar
[INFO]BAR packaging complete
(all paths excised)
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of
Michal Mocny
Sent: Tuesday, March 03, 2015 5:50 PM
To: dev
Subject: Re: [CLI] Default target when not specified for build
Defaulting to device might be problematic on iOS: sure we can detect
if a device is attached (using iso-deploy), but the build might fail
because a signing cert/provisioning profile is not valid (I think the
only way to check is to just build, I might be wrong).
The only guaranteed way it will
Currently `cordova run` on iOS defaults to emulator as well, like the
compile/build commands.
It's probably safe to say we never specified what happens when no
target is specified (thus right now the behaviour is not consistent
for all platforms) -- and this is a new feature request.
On Tue,