dsymutil failed with exit code 11

I'm having this with Xcode 5 GM. Disabling Script Debugging fixes this, but it's a bit a pain.

 

We have the exact same issue on OS X 10.8, Xcode 5 GM and Unity 4.2.1.
We've decided to disable script debugging in our beta builds for the moment.

 

Is there any progress on this issue?
We are having same issue with our project but, strangely, only when run target in xcode is set to our iPod 5G (iOS 6.1.3 - 10B329). And it does not happen with the same project and same steps but with run target set to iPad 1st generation (iOS 5.1.1 - 9B206).

PS.
xcode 4.6.3 (4H1503)
Unity 3.5.7f6 Pro

 

Actually, we cannot reproduce this device-dependent behavior anymore.

It seems that changing project settings in XCode - removing "armv7s" from "Valid architectures" or changing "iOS deployment target" - helps most of the time. But results also are not 100% stable.

 

This bug is still alive and well....

-OSX11
-Xcode 5.0
-Unity Pro 3.5.7

I would really like to use Unity for the purpose I've bought it for (make my development faster), not to be forced to jump over hoops everytime something new comes along. For this licensing fee I would expect you to up your game a bit.

Also, I hope the words "Upgrade to v4 Pro" aren't on the answer to this. Seriously, don't even go there right now!

 

I always do this now anyways, because it results in much faster xcode compilation. Not sure why people are treating this as some kind of showstopper / huge issue when it's as simple as changing the setting as shown above.

 

because you DO NOT have dSYM file?

When will it be finally solved??????????

 

We see the same issue with Xcode 4.5.2 and Unity 4.0.0f7.

 

I am having the same issue on xCode 5.0.2 and Unity 4.3. I can build it with dSYM if Script debugging is disabled, but whenever its enabled I have to change debug format to DWARF instead of DWARF w/ dSYM. Super annoying.

 

I haven't really found a 'solution' but I have found a few ways to work with this issue.

It seems when I deploy from Unity I receive this error completely at random. Here are a few things that I've noticed 'fix' the issue...

- In xCode, go to Product -> Clean... then try building... this attempts to regenerate the dSYM file... I had to hit the 'Play' button 3 times after 'Build Succeeded' before it would deploy

- In xCode after receiving the error, I walk away for about 3 minutes and came back and hit the 'Play' button... it deployed

- Sometimes changing the Build Options (Debug Information Format) from 'DWARF with dSYM File' to 'DWARF' and back, then cleaned and it deployed...

It never seems to be the same twice, but if you keep at it enough, you can make xCode feel all warm and fuzzy inside!

If anyone finds more consistent replication steps and ways to fix it, let us know...

 

I just had this problem again with xCode 5.0.2 and unity 4.3.1f1

 

Having the same problem on xCode 5.0.2 and Unity 4.3.2f1

 

Having the same problem with xCode 5.0.2 and Unity 4.3.1f1, doing a clean on the xcode project does not resolve the issue. Turning off script debugging in the Unity build settings dialog makes the issue go away.

 

Ditto.

 

Ditto here to.

I need the debug information to do a profiling to track memory leaks... Anyone have heard anything on the status of this? Is there anything we can do?


STILL NOT WORKING on version 3.3.f1 is there any hope of this ever getting fixed?

 

FYI,

I've started getting this error, and in my case tracked it down to async loading :

This generates the error:

Code (csharp):

1.    IEnumerator Start()
2.     {
3.         AsyncOperation load = Application.LoadLevelAdditiveAsync("PROPS");
4.         yield return load;

but this doesn't:

Code (csharp):

1.   IEnumerator Start()
2.     {
3.         Application.LoadLevelAdditive("PROPS");

I'm unable to submit a bug report just yet, but if anyone knows why the first code example would cause a fail (only with debug enabled), I'm all ears.

Edit: Unity Pro 4.3.3f1, Xcode 5.0.2, Mavericks

 

Same problem with XCode 5.0.2 and Unity 4.3.4

I added Chartboost and AdMob in my project.

 

This happens with XCode 5.0.2 too.