After my app is installed and while the logo is up, the Xcode debugger reports:
Program received signal: “EXC_BAD_ACCESS”.
If I stop the debugger and run the app by pressing the icon on my iPad it works just fine.
It’s only a mild annoyance, but it would just kill me to go through the whole development with this experience. Before I start a binary search (involving removing / readding everything half at a time), does anyone know why am I killing the debugger?
Hey, i had the same problem and think it was due to me forgetting to assign a var, which i should have done manually via the editor, and then trying to manipulate that unassigned var. In my case it was a GUIText.
can be a lot of things
I have gotten for forgetting a variable, wrong audio format / compression.
I also got it from upgrading a project from 1.7 to 3.0 with custom text issue.
It’s one of those errors that can be related to about anything from what i found trying to research it on various development forums.
Pretty much gonna have to rifle through the xcode logs i think.
In case of unity it normally means: You try to access a variable thats null (ie you try to access something not existing anymore)
what this is, is undefined, but if you do a debug build and check out the console log and callstack at freeze in xcode it will give you a rather good idea (class + function, potentially more).
this often helps you to replicate it right in the editor as well.
well the error just sorta disappeared after an awful lot of development.