Trying to build only for armv6 causes a EXC_BAD_ACCESS

MikeHergaarden · November 24, 2010, 10:12pm

I’m trying to build an ipad+iphone game for just armv6 to save filesize. However, after adding admob and iAd the game crashes in the preloader right after trying to load the next scene. It does not matter if both scenes are near empty.

If I change the Unity project setting back to “armv6 + armv7” everything works flawlessly.

Any clues/workarounds?
Being able to build for just armv6 could help me get under the 20mb limit.

EDIT
This seems to be a Unity 3.1 bug. It happens when adding admob to your iOS project. If you use iOS pro and enable build stripping this bug does not appear(!). I have reported this bug.

anon_11186168 · December 21, 2010, 10:31pm

Did you ever find a solution to this?

MikeHergaarden · December 22, 2010, 10:33am

Yes, it only happened for me when addign admob on archv6 devices or arcvh7 devices running a archv6 build.
This is a unity bug though: It does not happen when selecting any of the iOS pro build size stripping options. Switching build size stripping off crashes it again.

anon_64208319 · December 24, 2010, 12:11am

Might this be the same with my problem of getting EXC_BAD_ACCESS when just adding the Flurry-Lib to my XCode project? As soon as I am back from my vacation Ill have to try switching the stripping on too

anon_11186168 · December 24, 2010, 9:52am

Sweet! Thanks. Going to try that now- Then going back to sleep.

scritchy · July 2, 2011, 4:53am

Did anybody find a permanent solution for this??
I ran into this problem like Johannes with the flurry lib causing this.
My stripping was turned on, and no stripping setting is changing the outcome.
Only switching to armv6+armv7 fixes it, but this of course causes the app to be huuuuge.

thanks

macfinch · August 28, 2011, 5:14pm

Hey all.
Did anyone find a solution for this just using the basic Unity version?
I have the same problem when I try to add flurry just using the armv6 setting. It’s fine when I do armv6 + armv7. As I don’t have the Pro version I can’t use the stripping functionality.

Please let me know if anyone has any clues.

Thanks all
Martin

MikeHergaarden · August 28, 2011, 5:48pm

We decided to buy Unity pro, since on pro (with build size stripping) we do not experience any issues.
So this problem is still an issue in indie? annoying!

macfinch · August 28, 2011, 5:57pm

Yeah, still a problem :s
Will let you know if I find a solution to it.

Cheers
Martin

MikeHergaarden · August 28, 2011, 6:02pm

K :).
Do make sure to file a bugreport to Unity, don’t forget to attach a repro case.