Forum Discussion
Platform Command Line Utility tool bug
I'm glad that there is now a CLI tool for uploading builds. However, it seems that the current CLI tool's parameter parsing is broken (at least the application launch parameter parsing). If the beginning of your launch parameter string overlaps with any of the CLI tool's parameters (e.g., --launchparams "-server 127.0.0.1" in which '-server 127.0.0.1' overlaps with the tool's '-s' parameter) the tool will incorrectly parse the app's launch parameter as the CLI tool's parameter. In the example case I just gave, it appears that it will improperly parse two values for the app secret token: your actual app secret and "erver 127.0.0.1" - which ends up completely breaking the upload process, all of which can be observed in the tool's log file. If your app's launchparams were instead "-playback" - it would improperly parse your launch params to be "layback" - the upload might succeed, but your application's launch parameters will be broken.
For my case, this makes the CLI tool pretty much unusable for my app, as all of the command line parameters I need to specify start with either -s or -p. There are ways I could potentially address this on my end, but I'd rather not go through the contortions of dummy parameters or changing my app's command line parsing.
Is anyone else having issues with the build upload tool? Is anybody using it?
For my case, this makes the CLI tool pretty much unusable for my app, as all of the command line parameters I need to specify start with either -s or -p. There are ways I could potentially address this on my end, but I'd rather not go through the contortions of dummy parameters or changing my app's command line parsing.
Is anyone else having issues with the build upload tool? Is anybody using it?
7 Replies
- Sorry about this. Let me have someone take a look. Thanks.
- "Is anyone else having issues with the build upload tool? Is anybody using it?"
I've used it successfully, but didn't need to specify command line args to run in Rift mode. (the -l parameter). As far as I can tell the tool does seem to parse quotes correctly for other things like version number and release notes so I'm not sure why it would break down in your case. - Sorry, our documentation was incorrectly saying --launchparams but it should have said --launch_params.
Try doing --launch_params "-server 127.0.0.1" and it should work.
Thanks for reporting this bug. I've updated the documentation. - @boonefb - That fixed it! Thanks for the quick response.
A feature request that might help to stave off issues like this in the future: generate some warning/error output when the tool encounters unrecognized command line arguments? - @brockjones I'll look into adding that check. Thanks for the suggestion!
- @boonefb - Thanks! Now that I'm past the launch params issue, might there be a similar issue with documentation on the redestributable list parameter? When I use --redistributable <ID1>,<ID2>,... the tool does not seem to parse my list correctly. If I use -r instead, it seems to work fine.
- Yep it should actually be --redistributables :(
I'll update the documentation again
