Search Unity

Android libunity.sym.so errors in UCB

Discussion in 'Unity Cloud Diagnostics' started by MechEthan, Oct 18, 2019.

  1. MechEthan

    MechEthan

    Joined:
    Mar 23, 2016
    Posts:
    166
    Android release build on UCB for Unity 2018.4.10f1

    I got 4 errors about "no symbol section" and "decoding dwarf section info at offset 0x0: too short" for the libunity.sym.so file.

    See log subsection below
    ...
    6568: [Unity] Android PostProcess task "Zipping symbols" took 9599.5438 ms
    6569: [Unity] DisplayProgressbar: Performance Reporting Symbol Upload
    6570: time="2019-10-18T21:14:10Z" level=warning msg="Unable to retrieve dynamic symbols from file at Temp/StagingArea/symbols/arm64-v8a/libunity.sym.so
    6571: Error: no symbol section"
    6572: time="2019-10-18T21:14:10Z" level=warning msg="Unable to retrieve dynamic symbols from file at Temp/StagingArea/symbols/armeabi-v7a/libunity.sym.so
    6573: Error: no symbol section"
    ...
    6613: time="2019-10-18T21:14:11Z" level=warning msg="Unable to retrieve DWARF data from file at Temp/StagingArea/symbols/arm64-v8a/libunity.sym.so
    6614: Error: decoding dwarf section info at offset 0x0: too short"
    6615: time="2019-10-18T21:14:11Z" level=warning msg="Unable to retrieve DWARF data from file at Temp/StagingArea/symbols/armeabi-v7a/libunity.sym.so
    6616: Error: decoding dwarf section info at offset 0x0: too short"

    Does this mean my crash logs won't symbolicate?
     
    MechEthan, Oct 18, 2019
    #1

  2. Ryan-Unity

    Ryan-Unity

    Joined:
    Mar 23, 2016
    Posts:
    1,993
    Hi @Ethan_VisualVocal, you don't need to worry about those errors. The libunity symbol files are uploaded on Unity's side. We did have a bug with the upload process last week but have released a fix that should prevent any issues with libunity code lines not being displayed properly. Please let us know if that isn't the case and we'll take a look.
     
    Ryan-Unity, Oct 22, 2019
    #2
    MechEthan likes this.

  3. awyld

    awyld

    Joined:
    Jul 21, 2021
    Posts:
    1
    Hi, I'm having a similar issue upgrading our app from a 2019 version of Unity to a 2021 one; basically, what are the likely troubleshoot steps for these?
     
    awyld, Nov 3, 2021
    #3

  4. Rabadash8820

    Rabadash8820

    Joined:
    Aug 20, 2015
    Posts:
    94
    @Ryan-Unity I am also still experiencing these errors in Unity 2022.2. I know you said we can ignore them, but my Android build is still failing so it's hard to believe that they aren't at least a symptom of something deeper that I should be worried about. My build's full log is attached.
     

    Attached Files:

    Rabadash8820, Apr 19, 2022
    #4