iOS App Crashes on launch after second Unity Build

I am having this same Issue with 5.3.2f1 and 5.3.2.p3 with IOS devices running ARM-64. This only occurs on a Second Unity Build of the project using ‘BuildOptions.AcceptExternalModificationsToPlayer’ or Append of the xcode project.
This error can be worked arround if you only with arm-7 support. Is there a fix for this or other work around that will allow me to Append to a project and keep ARM-64 for AppStore Submissions?

@grag0042

Are you able to gather any more details about the cause of the crash? Is there a call stack available in Xcode when the crash happens? That might help isolate the cause.

Attached is a screen shot of Xcode when the app crashed on startup.

@grag0042

It is a bit difficult to tell the cause of the issue from this screen shot, but I think that the crash occurs somewhere in the Unity text rendering code. Can you copy the text of the call stack (on the left side of the Xcode window) and past it here? That will allow us to see the full function names.

I can make another screen shot of the call stack but some of the names are longer then Xcode will allow the box to extend. Is there another way to get the names in the call stack?

@grag0042

Yes, you can select all of the frames in the call stack and copy them as text. Then you can paste them here, and they should have the full names listed.

Here are the call stacks. Are these what you are looking for?

2527428–175312–1.txt (330 KB)
2527428–175313–2.txt (1.72 MB)

I went back through the code to try to find where/when this issue began. It stated when we went from Unity 5.2.2 to Unity 5.3.1/5.3.2

@grag0042

Sorry, these are not quite what I was after. I actually need the list of functions called. You can see them in Xcode in the gray section on the left, below the text “Thread 1”.

Unfortunately the text is not selectable to copy. attached are screenshots with the names.


2528704--175396--Screen Shot 2016-02-26 at 10.18.29 AM.png

@grag0042

Thanks, those screen shots work well! I’m not sure why this crash occurs or why it would be impacted by the Append option. Can you submit a bug report so that we can investigate this issue? It might be something complicated.

In the meantime, is it possible to work around the issue with ARMv7 or Replace?

If i export for only arm7 it doesn’t have this issue. If i use Replace it doesn’t have this issue. I have made a copy of the Xcode project directory before the append and compared it to after the append. There are a couple files that become drastically different.
This issue also only seems to affect on High end iOS devices ie. iPad Air, iPhone 6.

@grag0042

It sounds like a bug report is the best option for this case. This behavior does not seem correct.

I have tracked it down to Google Cardboard 0.5.0.
If cardboard 0.5 is installed it will cause this issue.

@grag0042

That is interesting. I’ve not heard of any issues with with cardboard yet. Can you submit a bug report still?

I have submitted a bug report

Thanks!