Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I am running Xamarin Studio on a Mac (Yosemite 10.10.3), running the stable branch everything runs just fine but if I update to the Alpha branch (8.10) I am unable to run any iOS application (Phoneword for example) on simulator or device. If I roll back to stable branch all runs good again. Xamarin Studio displays "Waiting for debugger to connect..." and then just quits. Below is the message in Application Output window.
Starting iPhone 4s
Failed to launch the simulator: Could not find a part of the path "/Users/orgbrat/Work - Xamarin/Part5.Completed/Phoneword/bin/iPhoneSimulator/Debug/"/Users/orgbrat/Work - Xamarin/Part5.Completed/Phoneword/bin/iPhoneSimulator/Debug/Phoneword.app/Phoneword"".
error MT1008: Failed to launch the simulator: Could not find a part of the path "/Users/orgbrat/Work - Xamarin/Part5.Completed/Phoneword/bin/iPhoneSimulator/Debug/"/Users/orgbrat/Work - Xamarin/Part5.Completed/Phoneword/bin/iPhoneSimulator/Debug/Phoneword.app/Phoneword"".
@Rolf I believe this is what you fixed recently ? if so was it backported to C5 ?
@Steve can you try renaming your project directory to avoid spaces inside them ? The "quoting" for it was misapplied for the API being used (which is why the path looks weird).
@Sebastien that was the issue. Made sure directory path had no folder with spaces and everything worked as it should. Thank you very much for the help. Is there a fix coming for this issue?
Thanks for confirming! I'm fairly sure it's already fixed, we just need to confirm which version is scheduled to include it.
*** This bug has been marked as a duplicate of bug 29206 ***
@Steve, this bug is a candidate for the first service release (8.10.1.x).