Unity cloud problems with symbols

Unity
1

Hi there!

I have been unable to use the FMOD libraries with Unity Cloud Diagnostics for symbolication. After verifying with llvm-readobj, I confirmed that neither the .so.debug files nor the runtime .so libraries contain a GNU Build ID—which Unity requires to match symbols with native crash reports.

As a result, while the symbol upload completes successfully, Unity Cloud shows “no images found” and fails to symbolicate FMOD-related crashes.

Would it be possible to provide updated versions of the FMOD Unity libraries (Android, arm64-v8a) that include a GNU Build ID? Specifically, these files:

libfmod.so

libfmodL.so

libfmodstudio.so

libfmodstudioL.so

Alternatively, if debug .so files with Build IDs aren’t available, could you share a symbol map for these binaries? This would allow me to manually resolve crash offsets.

Having either of these would greatly help diagnose native crashes involving FMOD in production builds.

We are working with version 2.02.28 and using the symbols given by you in a past ticket.

Thanks again for your support!

2

Thanks for the heads up about Unity cloud, that’s good to know. I can confirm our 2.03 builds include a build-id, but as you’ve discovered our 2.02 builds do not. I’ll see if I can get that build ID added for our next release.

1 Like