- #Apple iphone emulator for mac for mac
- #Apple iphone emulator for mac simulator
- #Apple iphone emulator for mac windows
The simulator is not set to auto start or anything like that. What really gets me is if I reboot the Mac, don't open the Simulator and start Visual Studio for Mac, then open a solution, I still have to go through the close/re-open solution steps. It still feels like a bug to me, I don't see why I would have to close/open a solution multiple times to get the iOS devices listed and be able to run an iOS app. I don't even have to close the Simulator if it's already running, which saves a bunch of time. I think I've counted up to 5 times before it finally worked), it will start showing the device list and I can run the iOS app in the Simulator.
#Apple iphone emulator for mac for mac
For now, I'm working on a single Xamarin Project on the Mac (and I don't use the Mac for anything else), So I just let Visual Studio for Mac 'open at login' (Dock setting) and automatically 'load previous solution on startup' (Visual Studio for Mac setting), hide Visual Studio for Mac (Dock Setting) and if I need it, Visual Studio for Mac is already loaded and able to see iOS Devices to run Apps on with a quick click on the Dock Icon.Īddendum 2 (final?): I have now found that if I just close a solution that I have open that shows 'Generic Simulator' and re-open it without exiting Visual Studio for Mac (sometimes I have to do it multiple times. If there really were a 'caching issue' with the Simulator it seems to me I should have problems running anything on the Mac after using the iOS Simulator from Windows, but it always works. In addition, I can leave Visual Studio for Mac running (even hidden) and test an app on the iOS Simulator from Windows, then, leaving the iOS Simulator Running on the Mac, run an App on Visual Studio for Mac.
#Apple iphone emulator for mac windows
The reason I say that is I can ALWAYS see the iOS Device list from Visual Studio for Windows (as long as I can connect to the Mac). I sometimes delete the tmp*.binlog and tmp*.tmp as a last ditch effort before using the 'xcrun simctl erase all' command to try to get back to where Visual Studio for Mac will see the iOS Simulator Devices.įinally: This is really starting to feel like a bug in Visual Studio for Mac startup (or possibly during a iOS project load). The directory where they were created is the 'T' folder I'm talking about). binlog files that are written in the 'T' folder will sometimes fix the problem (if you look at an IDE log from Visual Studio for Mac right after the 'The target name of simulated device could not be added because it's already cached' message, you should see some. But occasionally I still have to clear the cache from the Terminal with 'xcrun simctl erase all' command.Īlso: I have also found (although maybe it's just my imagination) that clearing out the Visual Studio for Mac temporary. And the Simulator starts up substantially quicker then if I did a 'xcrun simctl erase all' command from Terminal.Īddendum: Most of the time the above works. It still isn't great, but this has (so far) always worked for me. try the above steps one more time (this time you should only have to close Visual Studio for Mac followed by manually starting the Simulator, waiting for it to start, and then quitting the Simulator and finally restarting Visual Studio for Mac).
it ends up being simpler and quicker than anything else I have found. but you may just want to go down to the Addendum 2 (final?) and see if that works for you. You are welcome to read through all of this.
'The target name of simulated device could not be added because it's already cached'. Looking at the Visual Studio for Mac logs, specifically the IDE log, I found this line.