I agree that it would be better to just run the tools that are part of the development toolchain. I have been trying to remove all of the special tooling and only kept that last step of running it on multiple devices (see reasons below). There are other issues with the ios-deploy that I have not yet resolved. It has an enormous delay in the middle of it and I have found that deploys are significantly less reliable since I switched to it. About 30% of the time it just hangs near the run command and the deploy fails.
If you want to add the dependency script as a short-term measure, thats fine. In the long term I think we need to fix the command line tools to support the automated deploy properly on all platforms. -- notes -- It may be possible to use the ios run command line components, but when I first looked at it there were some issues. The easy solution seemed to keep the little bit of special code from Medic. As I recall: * no support for obtaining a list of devices attached * no support for deploy only (dont build) - all of the commands want to prepare/build and that causes problems * Medic needs to wrap each deploy in a timer to kill it if it doesnt complete. On Fri, Nov 1, 2013 at 8:46 AM, Sergey Grebnov (Akvelon) < v-seg...@microsoft.com> wrote: > Hi David, > > Do we really need 'ios-deploy' module since 'cordova-cli' should support > installing and listing connected devices, isn't it? I think it is better to > use cordova-cli for such tasks since we also test this functionality as > part of the tests preparation process. > > Due to 'ios-deploy' reference I can't install Medic on Windows platform; > as a quick temporary solution we can move 'ios-deploy' dependency to > devDependency so I can run 'npm install --production' and it will be > skipped, but the better option seems to be adding additional > install_dependency.js script like suggested at [1]. > > David, what do you think the best option to have Medic run on both Mac and > Windows platform? > > [1]http://stackoverflow.com/a/15670089/255654 > > Thx! > Sergey > -----Original Message----- > From: drk...@google.com [mailto:drk...@google.com] On Behalf Of David Kemp > Sent: Monday, October 28, 2013 6:53 PM > To: dev@cordova.apache.org > Subject: Re: Medic / fruitstrap /xcode 5 > > The cordova-medic project has been updated to use the npm version of > ios-deploy. > > Also, separate tests for CLI and plugman have been added. > > > On Mon, Oct 28, 2013 at 10:20 AM, David Kemp <drk...@google.com> wrote: > > > When I run this tool like: > > > > ios-deploy --id xxxx --bundle xxx --debug > > > > it works, but there is a ~45 second pause after run/success before the > > mobilespec application actually starts running the test. During that > > time the cordova bot image is on the device (so something has started). > > > > There is no debug output for this time, but at the end of the delay > > everything moves along as expected. > > > > Any idea whats up with that? > > > > > > > > On Fri, Oct 25, 2013 at 6:28 PM, Shazron <shaz...@gmail.com> wrote: > > > >> related: xcode 5 command line tools however, have a way to deploy to > >> a device directly but *only* for running XCTest based tests > >> (xcodebuild -destination [destination-specifier]) > >> > >> > >> On Fri, Oct 25, 2013 at 3:23 PM, Shazron <shaz...@gmail.com> wrote: > >> > >> > http://github.com/phonegap/ios-deploy > >> > or from npm install -g ios-deploy > >> > > >> > This is used in cordova-ios > >> > > >> > > >> > > >> > > >> > On Fri, Oct 25, 2013 at 1:58 PM, David Kemp <drk...@chromium.org> > >> wrote: > >> > > >> >> Hi all, > >> >> It seems that xcode 5 no longer supports gdb, resulting in > >> >> fruitstrap > >> not > >> >> being able to deploy iOS apps. fruitstrap seems to have a > >> >> hard-coded > >> path > >> >> to where the appropriate gdb bits are. > >> >> Our test system is currently not running iOS tests for that reason > >> because > >> >> xcode conveniently upgraded. > >> >> > >> >> I am looking into solutions, but thought someone out there might > >> >> know a fix. > >> >> > >> >> Thoughts? > >> >> > >> >> David Kemp > >> >> > >> > > >> > > >> > > > > >
