My game was working perfectly for months, I even had it on my iphone. No errors or warning in Unity or xcode. Then one day I get this dreaded mach o linker error from no where, so I update from Unity 4.6.1 to 4.6.7, and xcode 6.3 to 6.4. Now I’m getting this error and because I have very little programming knowledge (ESPECIALLY with anything Apple related–xcode, swift), I have no idea what to do. I’ve searched this error and read every piece of advice and info on it, and what all it seems to come down to is debugging. The problem is I don’t know how to navigate xcode any further beyond building my project form Unity to xcode and then uploading to the appstore. Also, why would it work flawlessly before and now all of a sudden I’m getting this error? I keep thinking it’s because I updated it (I always get these random, rare, inexplicable errors), but if that’s unlikely, would someone please be willing to look over my code? Or help in any way, really. It’s such a simple 2D game, but I can’t tell you how crushed and stressed I feel at this point.
I can’t tell what the exact cause of the bug is, but I have a vague recollection that we corrected a similar looking crash in IL2CPP recently. It may be worth trying the latest Unity patch release (4.6.7p4, available here: http://unity3d.com/unity/qa/patch-releases), or the 4.6.8 release of Unity, which should be out soon.
Hmm didn’t work, should I just wait for 4.6.8? I also tried going back to an older version of xcode that didn’t give me this problem, but I went as far as 6.3 and it’s still giving me the problem, so I’m having a lot of trouble finding the cause of this error.
Unfortunately, I don’t think that 4.6.8 will be better than 4.6.7p4 in this case, as 4.6.8 does not have any additional IL2CPP fixes. If possible, can you submit a bug report with a project that reproduces this issue? Also, does a similar problem happen with the Mono scripting backend?
Huh guess my post didn’t go through so I’ll re-reply. Ok so I submitted a bug report! Hoping to hear back soon. I did try switching back to Mono, and that results in the mach o linker error.
@JeffGordonRamsay hmmm. Looking at the stack on the left. I see what might look like a crash in your collider. Did you go through to make sure you didn’t a null pointer somewhere?