-
Notifications
You must be signed in to change notification settings - Fork 987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace ios-deploy with node-ios-device #488
Conversation
* @param {String} appPath Path to application package | ||
* @return {Promise} Resolves when deploy succeeds otherwise rejects | ||
*/ | ||
function deployToDevice (appPath, target, extraArgs) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was extraArgs
used for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extraArgs
contained the arguments not used by run.js
.
It allowed to pass arguments to ios-deploy
(ios-deploy usage).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, so with your PR we loose this functionality. Which use case did it cover? What will not work any more for users that might be using this right now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think extraArgs
is safe to ignore -- this would be any extra arguments to pass ios-deploy
which we don't really officially support, but was "nice to have". If you do a cordova run --help
you would see its the POPTS
, which is not defined, thus we don't have any specific platform options.
We will have to remove any extraArgs
code here as well:
cordova-ios/bin/templates/scripts/cordova/lib/run.js
Lines 101 to 106 in 1d00e60
var extraArgs = []; | |
if (runOptions.argv) { | |
// argv.slice(2) removes node and run.js, filterSupportedArgs removes the run.js args | |
extraArgs = module.exports.filterSupportedArgs(runOptions.argv.slice(2)); | |
} | |
return module.exports.deployToDevice(appPath, runOptions.target, extraArgs); |
This comment has been minimized.
This comment has been minimized.
7d0d5a8
to
d8cd743
Compare
Codecov Report
@@ Coverage Diff @@
## master #488 +/- ##
==========================================
- Coverage 75.66% 75.27% -0.39%
==========================================
Files 11 11
Lines 1796 1792 -4
==========================================
- Hits 1359 1349 -10
- Misses 437 443 +6
Continue to review full report at Codecov.
|
Testing this right now. |
Doesn't seem related, but I have an error with the below. Will debug:
|
(UNRELATED) Ok, so it seems this line fails to delete a symlink:
require('fs').unlinkSync(appFile) and now the app can deploy.
However, even though the app deploys, it does not launch the app like |
@shazron |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though it installs the app, it does not launch it -- so this is one loss of functionality. It was suggested ioslib
could do this, but from what I can see it can only launch for simulator.
I will close out this ticket because:
I still want to thank you for the effort you put into this. |
Closes #419, #420
Fixes #429
What does this PR do?
Replaces
ios-deploy
withnode-ios-device
.Removes a global dependency.
Checklist