I’m on OSX 10.10, using Unity 5.1.2p3, when I build and run, the built app will crash.
I tried restarting, reinstalling, and with a few projects. Always same result. Apple crash report says the following:
Is this happening for anyone else?
I am such a dimwit.
it was set to x86
macs have not run on 32bit since the dark ages, not sure why this option even exists or why it was selected!
Just because the OS is 64-bit doesn’t mean 32-bit code can’t run. It works fine here. If it crashes then it’s a bug somewhere.
–Eric
You’re saying you can build x86 on mac from unity 5 and it doesn’t crash the builds?
If you have a version of Unity 5 without the 32-bit build crash bug, sure. There’s nothing about OS X being 64-bit that prevents it from running 32-bit code.
–Eric
Are you saying you can do it? Or just in theory? Because in reality it doesn’t work. 
It does, though. Unity 5.0 produces working 32-bit apps.
–Eric
x86 (32) builds will not work on OS X. Actually we have problems even with x86_84 builds on OS X.
5.1.2 will not work for sure, there is a bug in that version. In 5.1.3 new projects compile (x86_84) and work perfectly, while old one (at least our project) will not. x86 will not work in 5.1.3, only debug versions do.
Dev team is trying to find the problem.
Ah thanks for confirmation Maverick, sometimes it’s hard to know with Mac problems.
At first I thought it might be the IL2CPP setting, but that is only available on iOS build settings, which now require it. Maybe there is something broken with the Mono2x on desktop since that was implemented?
(not that we need to compile to 32bit on OSX, but yes it is broken for me too)
x86 (32) builds absolutely do work on OS X. Not with the latest version Unity 5.1, because of a bug. But Unity 5.1.0f2 at least, and 5.0, export both 32 and 64 bit builds without a problem. If you like, I can upload a build somewhere proving it. Presumably the bug will be fixed in an upcoming version.
–Eric
Willing to test if you want to upload one
That does indeed appear to work with no problems.
Upgraded to 5.1.3f1 and did my own test, crashed. Seems recent versions are broken.
https://www.dropbox.com/s/4tiikmqxj0vkoi2/test32bit.zip?dl=0
5.1.3f1 actually fixed 2 major game breaking bugs so not rolling back anytime soon.
Hello,
We’re getting a build error on OSX with the latest version of Unity
“01/09/2015 10:37:11.000 test[1939]: dyld: lazy symbol binding failed: Symbol not found: _mono_set_dirs
Referenced from: /Users/rob/Desktop/test.app/Contents/MacOS/test
Expected in: /Users/rob/Desktop/test.app/Contents/MacOS/…/Frameworks/MonoEmbedRuntime/osx/libmono.0.dylib”
and
“01/09/2015 10:37:11.000 test[1939]: dyld: Symbol not found: _mono_set_dirs
Referenced from: /Users/rob/Desktop/test.app/Contents/MacOS/test
Expected in: /Users/rob/Desktop/test.app/Contents/MacOS/…/Frameworks/MonoEmbedRuntime/osx/libmono.0.dylib”
Deadline is fast approaching - so any help would be greatly appreciated.!