Search Unity

UCB build fails - An error occurred while resolving packages - Firebase

Discussion in 'Package Manager' started by codematic, Jul 10, 2020.

  1. codematic

    codematic

    Joined:
    Feb 26, 2017
    Posts:
    12
    Hello.

    Suddenly today our builds are failing due to:

    [Package Manager] Done resolving packages in 37.00s seconds
    73: [Unity] An error occurred while resolving packages:
    74: [Unity] One or more packages could not be added to the local file system:
    75: [Unity] com.google.firebase.analytics: shasum check failed for /BUILD_PATH/Library/Unity/cache/npm/unityregistry-pa.googleapis.com/.tmp4033EFKYDkIc2OF9/tarball/package.tgz
    76: [Unity] Expected: 95847f32e45ffdfe101af4973a0d2ced14ff79ef
    77: [Unity] Actual: 42eccea87176e7b409e0a1c9725ddcd39bab3724
    78: [Unity] com.google.firebase.app: shasum check failed for /BUILD_PATH/Library/Unity/cache/npm/unityregistry-pa.googleapis.com/.tmp40331waxcNGdxvLE/tarball/package.tgz
    79: [Unity] Expected: 4e8a8c568507ba720c7a11803324c06ecfd074ee
    80: [Unity] Actual: 1a5b813d4a93cda621cad0787251cd70363a8e19
    81: [Unity] com.google.firebase.dynamic-links: shasum check failed for /BUILD_PATH/Library/Unity/cache/npm/unityregistry-pa.googleapis.com/.tmp4033BW66XmMbrt2b/tarball/package.tgz
    82: [Unity] Expected: 29941dff09f34264439bf7127d36198006b80756
    83: [Unity] Actual: c02b5b531007c8f5847269055171e348196d221b
    84: [Unity] com.google.firebase.messaging: shasum check failed for /BUILD_PATH/Library/Unity/cache/npm/unityregistry-pa.googleapis.com/.tmp4033VpC6PGinaZKy/tarball/package.tgz
    85: [Unity] Expected: 4f66700ce3fce82f56a63114afcb63e18db08ab7
    86: [Unity] Actual: 4f36766904a331628515b69131656d16f6a0d247
    87: [Unity] A re-import of the project may be required to fix the issue or a manual modification of /BUILD_PATH/codematic.warfield.android-uat/Unity-WarArena/Packages/manifest.json file.


    Anyone has the same problem? Know maybe how to fix it? Looks more like UCB problem itself.

    Thanks
     
  2. dirty-rectangle

    dirty-rectangle

    Joined:
    Apr 23, 2015
    Posts:
    78
    I've seen the same issue in cloud build today, A workaround fix for this is to embed the two packages in the Packages folder.
     
  3. Anhnh1721

    Anhnh1721

    Joined:
    Nov 18, 2015
    Posts:
    5
    Me too. I cannot add Firebase SDK to the project via Package Manager

    Screen Shot 2020-07-10 at 23.42.27.png
     
  4. BBIT-SOLUTIONS

    BBIT-SOLUTIONS

    Joined:
    Feb 21, 2013
    Posts:
    39
    Have the same error when trying to add any firebase package to the project via package manager:

    Code (CSharp):
    1. Cannot perform upm operation: shasum check failed for C:\Users\<Username>\AppData\Local\Unity\cache\npm\packages.unity.com\.tmp482852R1HwdNRnNegr\tarball\package.tgz
    2. Expected: 4e8a8c568507ba720c7a11803324c06ecfd074ee
    3. Actual:   1a5b813d4a93cda621cad0787251cd70363a8e19 [NotFound]
    4. UnityEditor.EditorApplication:Internal_CallUpdateFunctions()

    Edit: Seems only to occur with Firebase version 6.15.1. Version 6.15.0 works without problems. Maybe this information helps somebody.
     
    Last edited: Jul 10, 2020
  5. codematic

    codematic

    Joined:
    Feb 26, 2017
    Posts:
    12
    thanks, that is good workaround
     
  6. nmd2

    nmd2

    Joined:
    Mar 19, 2019
    Posts:
    13
    Same problem, 6.15.0 crashes the editor on second run though, so I hope they fix soon.
     
  7. fivmax

    fivmax

    Joined:
    Apr 14, 2020
    Posts:
    1
    I'm also seeing this error with 6.14.1 while building with a Github action, so it doesn't necessarily seem related to UCB.
     
  8. BBIT-SOLUTIONS

    BBIT-SOLUTIONS

    Joined:
    Feb 21, 2013
    Posts:
    39
    Update: They seem to have fixed it for the latest version 6.15.2
     
  9. nmd2

    nmd2

    Joined:
    Mar 19, 2019
    Posts:
    13
  10. KislunA

    KislunA

    Joined:
    Sep 4, 2020
    Posts:
    1
    May be rolling back to prev. working version (by manually edit manifest.json) & then update version up again will fix such problem. (the simptoms looks like apckage authors unpublished, and then published again this version - so it got new shasum, but Unity somewhere remember old value). I'm interesting - where?