Search Unity

Still have issues with arm64e on Unity 2018.4.5

Discussion in 'Unity Cloud Diagnostics' started by stopiccot_onthespot, Jul 30, 2019.

  1. stopiccot_onthespot

    stopiccot_onthespot

    Joined:
    Oct 1, 2016
    Posts:
    68
    I've migrated my game to Unity 2018.4.5f1 to fix the arm64e issue

    I've received crash from arm64e device (iPhone Xs):
    screen1.jpg

    Seems like there is no symbols for uuid: 03d55584c7d03ef0bde331d56a0b39c4
    But according to usymtool log symbols for that uuid were successfully uploaded:
    screen2.jpg
    I even manually uploaded them:
    screen3.jpg
    But still no luck symbolicating. Can I provide any more info to fix the issue?
     
  2. stopiccot_onthespot

    stopiccot_onthespot

    Joined:
    Oct 1, 2016
    Posts:
    68
    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. screen.jpg
     
  3. stopiccot_onthespot

    stopiccot_onthespot

    Joined:
    Oct 1, 2016
    Posts:
    68
  4. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,220
    Hi @stopiccot_onthespot, 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.