Setting up a Mac development build system on Windows using VirtualBox and Mojave. I got everything installed correctly, and it’s basically functioning fine, but whenever I try to build a project or do anything memory intensive in Xcode, it just freezes and beachballs. I never get any error messages or anything, and it does it on different types of projects. I have 8GB of RAM allocated, so I think that should be sufficient. Anyone running to this issue? Thanks!
Host: Windows 10
Guest: macOS Mojave
Switched to a High Sierra VM and it’s working alright now, guess the Mojave VM isn’t as stable or something.
Related
I recently got a new computer - macbook, 2020, m1 chip, running Big Sur, and I wanted to install a windows 10 64-bit guest on virtualbox on it. However, no 64 bit options of any kind appear in the menu when I try to create a new machine. On my old computer, virtualbox still seems totally capable of creating and running a 64-bit guest. I noticed other people had this issue, but there was no clear explanation for how to fix this if the host is a mac. There seemed only to be fixes for Windows Users. Is there anyway to fix this?
Although I know that this Xcode version is quite old, my company's project still needs to use it and I didn't manage to make it ran properly on my company's mac.
Does anyone have faced this issue as well? Any idea would be very helpful!
ps. On my personal mac, with macOS High Sierra 10.13.1 Beta (17B25c), every time that I try to open Xcode 7.3.1, it crashes and doesn't even inform the reason.
It works on my machine... I know that doesn't help you but I just installed it and it opens ok. Maybe upgrade to full version?
After running Xcode 7.3.1 on MacOS High Sierra 10.13 VM, I can confirm that I can compile and run build on Simulator and devices with iOS6 & iOS7.
Unfortunately, there is no Cross-Compability-Guide to downgrade to older Development Environment or generell Software on newer Mac, because only minimum Requirements are listed in wikis like this:
https://de.wikipedia.org/wiki/Xcode
So, my tip on this topic is really to use older Hardware to test on matching Environments or try Virtualisation such as Parallels, Fusion or Virtualbox.There are differents in Virtualisation too. If some Virtualisation fails e.g. Virtualbox, maybe another Program (e.v. Parallels) does the job well.
I really use older Mac Hardware for testing older Software-Versions and that is the best tip I can give you on this topic. So its a good idea to have an older Hardware Repository to do this jobs, on which virtualization fails.
I know some Apple Developer which use some older Mac minis in their basement - remote connected - to solve problems like this.
Asking this on SO as well as the Unity network, hoping someone can give me a hand.. I'm running into an issue that seems to be specific to 4.6.x versions of Unity. First, the specs: I'm running a Mac Mini with an i7 Processor, 8GB of ram and OS X Yosemite.
Now, I've been able to run Unity 5.x without any issues (This is my last resort, If I have to I'll end up running Unity 5.x, but I'd rather run 4.6.x), but when I attempt to run any Unity 4.6.x version, the editor application itself attempts to start up, and immediately crashes. I've attempted uninstalling & removing preferences, rebooting, different versions, etc to no avail. Has anyone run into this issue before, if so what was the fix? I've heard that this was a known issue at one point, but was fixed in Unity 4.6.1 (which I've attempted to run unsuccessfully...)
Thanks!
I'm trying to install Xcode in a VirtualBox Hackintosh for app development purposes. I used MultiBeast and the Xcode installation is complaining about the display, but the way VirtualBox handles displays and graphics is beyond me.
I get the following error: Xcode: CVCGDisplayLink::setCurrentDisplay didn't find a valid display -- falling back to 60Hz.
I've currently followed the installation instructions from this link. I'm not sure if it makes a difference but my host is ArchLinux with Intel Haswell with Iris Pro Graphics.
Why am I getting this error?
Hmm.. not sure if this is right or not. I did this, and it fixed something:
from http://www.macbreaker.com/2012/07/mountain-lion-virtualbox.html
You need to change the CPUID to a non-Haswell ID to fix the issue
non-booting 10.8 on a Haswell CPU:
VBoxManage modifyvm {your vm name here} –cpuidset 00000001 000106e5 02100800 0098e3fd bfebfbff
But I'm having some trouble remembering the exact chain of events. It might've been another tweak later on that got XCode to install properly.
Regardless, I feel dirty for even attempting to do this. I hoped I would never be put in a situation where I had to cheat on Linux, but it beats spending over a grand (despite that mine is top-notch) to work on a useless iPhone app. In other words, it sucks being an independent commodity producer.
I'm getting the same error, but on actual Apple hardware.
Despite that, the display link object does seem to work.
Maybe it's because it is not familiar with my Dell monitor.
I am brand new to Apportable. I installed and am able to launch the sample Spin app on my Android device. However, after launch, my system is completely frozen and will not respond to any trackpad or keyboard touch. I hard booted and tried again with an iOS app I developed with the same results.
System:
MacBook Pro 15" Early 2011 running OSX 10.9
16GB RAM, 20 GB disk space available
Xcode 4.6
Any ideas why this is happening and what I can do to prevent it? Thanks!
Sometimes while copying the apk to the device, the USB driver gets blocked for a few seconds. If this is the same issue, then your system should return to normal pretty quickly (no more than five seconds on most machines).
If that isn't the case for you, you can try the following command:
MTP=no apportable load
If you still have the issue after that, something else is going on that I have never seen.
I had the same problem and MTP=no apportable load solved it for me.