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'm trying to run UITests locally on a iOS 7.1 simulator (I just tried iPhone 5s and iPhone 4s with the same issue) and just get the following returned:
As another bug to add to this, I can right click and "Copy" the text but then it won't actually copy it to allow me to paste it.
Running the application on the iOS 7.1 simulator works as expected. Log files do not contain anything useful for helping out with this error:
I can reproduce this problem with the missing directory when the iOS 7.1 simulators are freshly installed.
It looks like when you install the iOS 7.1 simulators the Applications directory is not yet created:
The data directory just has Library, var and Media subdirectories in it.
If you run the iOS simulator from Xamarin Studio first before trying to run it with UITest then the Applications directory gets created. Not sure who should be triggering the creation of the Applications directory.
After debugging/running the app once you can get passed the missing directory error but I then hit an "Instruments failed to start the app".
For some reason, I've got three different iOS 7.1 devices for each device type, so when I hit run and debug, it uses one GUID and then when I use the UITest Test Runner, it uses another device.
Whilst the workaround is straightforward (now the problem is understood), we should make sure that XS uses the same selected device GUID for both running the app in the simulator and running the UITest tests.
Can you coordinate with Jeff to fix this?
Fixed in version 18.104.22.1682 (master)
Author: Matt Ward
Commit: a5c0186e5fc11b4950b08017b21a86e56e9731ef (xamarin/md-addins)
Included in Commit: ff619c0d81e3316eff6c026fc34d2deefca1b159 (mono/monodevelop)