Still have issues with arm64e on Unity 2018.4.5

Unity Services
,
1

I’ve migrated my game to Unity 2018.4.5f1 to fix the arm64e issue

I’ve received crash from arm64e device (iPhone Xs):

4800347--458894--screen1.jpg
4800347--458894--screen1.jpg2090×1410 379 KB

Seems like there is no symbols for uuid: 03d55584c7d03ef0bde331d56a0b39c4
But according to usymtool log symbols for that uuid were successfully uploaded:

4800347--458900--screen2.jpg
4800347--458900--screen2.jpg2270×308 145 KB

I even manually uploaded them:
4800347--458903--screen3.jpg
4800347--458903--screen3.jpg1604×754 70 KB

But still no luck symbolicating. Can I provide any more info to fix the issue?

2

Looks, like it’s not even an arm64e specific issue. iPhone 6s has the same issue but at least system calls had been symbolicated this time. I think there is some issue with system calls not being symbolicated on iOS 12.4 crashes.

4800455--458909--screen.jpg
4800455--458909--screen.jpg2148×1256 309 KB

3

Hey @Ryan-Unity

4

Hi @stopiccot_tds , we uncovered an issue where our symbol nodes were running out of memory, preventing proper lookups of symbols for incoming crash reports. We’ve fixed this issue as of half an hour ago and, while this won’t fix the missing stacks for existing reports, all incoming reports should now have the missing symbols replaced. We’re sorry for the inconvenience.