usymtool Segmentation Fault on M1 Mac

Unity Services
,
1

We are trying to run an iOS Build with Unity Cloud Diagnostics enabled but the build is failing on the **process_symbols.sh** step. From reviewing the log it looks like a segmentation fault is being triggered by usymtool and seems to only be happening on a newer mac that uses the M1 processor. Is anyone else running into this or know of a work around aside from disabling Cloud Diagnostics?

Here is the output from the log:

"$PROJECT_DIR/usymtool" -symbolPath "$DWARF_DSYM_FOLDER_PATH/$DWARF_DSYM_FILE_NAME"
Command PhaseScriptExecution failed with a nonzero exit code```
2

Same here. Unity 2019.4.16f

3

I have the same error. may be the ‘usymtool’ has not support with mac m1.

4

I also think like that, so I’m getting some way to skip this step.

5

Did you find away around this?

6

I’ve filed a bug report, it’s not yet fixed in any version I’ve tried so far. The only solution would be to turn off cloud diagnostics which is not an option for a live project.

7

duplicate thread: usymtool can not run on mac m1 silicon !

8

Hello did anyone solve this issue, already? It’s messed up.

9

It happen to our project too.
And it only happen when using Unity batchmode to build iOS project.
It won’t happen if build with Unity editor(i.e. Build Setting → Build)

1 Like
10

I also had the same issue.
Did you find a solution?

11

Hi, someone find solution?

12

https://issuetracker.unity3d.com/issues/macos-m1-segmentation-fault-error-is-thrown-when-running-the-usymtool-on-a-m1-machine look like fixed

13

Hi frbodya,

Yes, this issue has been resolved in Unity 2019.4.25f1 and all proceeding versions. Please let us know if you have any additional questions.