[ 
https://issues.apache.org/jira/browse/CB-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551583#comment-14551583
 ] 

Shazron Abdullah commented on CB-8730:
--------------------------------------

I want to change the workflow on how this works for iOS, based on the ML 
discussion.

In essence, iff a device is connected, deploy to it, if not deploy to the 
Simulator.

To prevent requiring ios-deploy even when you only want to run Simulators, in 
lib/run.js, we can call listDevices and check if the array is empty (this 
assumes list-devices still uses the system-profiler call).

If a device is connected, build the project, and push the "--device" flag in 
argv. If not, remove it. This saves on build times.
If a device is connected, deploy to the device, if not deploy to the Simulator.








{code}
check_reqs_ios_deploy().then(function() {
}).then(function() {
}).then(function() {
}).then(function() {
}).then(function() {
})
{code}


> Can't deploy to device 
> -----------------------
>
>                 Key: CB-8730
>                 URL: https://issues.apache.org/jira/browse/CB-8730
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 3.8.0
>         Environment: OS X Yosemite 10.10.2, iPhone 6, 6+ on 8.1.2 and 8.1.3 
> (did not test on 8.2)
>            Reporter: Hirbod
>              Labels: cordova-ios-4.0.x
>
> Hi,
> before iOS 3.8.0 I was able to run my app with "cordova run ios". This would 
> install the app on my iPhone. Now it just launch the simulator.
> Actually, it should only run the simulator when no phone is attached.
> I've also updated to ios-deplay 1.4.0.
> The only way to deploy on phone:
> cordova run ios --device
> But the device parameter wasn't required before. Is this behavior as expected 
> or a bug?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to