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?