Running Rift build with Unity still open issue(s)
Is there a way to bypass this message: In the past it could run Unity in the background while I tested out some things within my builds. We're supporting Go and Rift so from time to time I'll send an invite over to the Rift on the Go to test out cross-functionality and then I'll get prompted with that when I try to accept the invitation. I've got multiple unity instances open usually when I'm working on things and to have to close them out everytime when I'm testing things is rather annoying. I don't suppose anybody else has run into this issue before and has a solution? It seems as though this is somewhat recent.
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?
Preview build unavailable to some developers
I've got an alpha channel build and I've added some of my colleagues to it, but it only shows as unavailable without explanation when they try to install it from the preview builds section in the Oculus store app. Both have the "unknown sources" switch enabled. Is there any way to debug this? I can install it myself no problem, and I don't even have a headset attached on my machine.
