Search Unity

Bug iOS builds fail on multiple projects - ERROR: Addressable content build failure - SBP ErrorError

Discussion in 'Unity Build Automation' started by Revolter, Dec 5, 2022.

  1. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    216
    Suddenly my iOS builds (different unrelated projects) started failing over the weekend with the same error.

    Anyone having the same issue?

    Code (CSharp):
    1. 53828: [2022-12-05T09:26:23Z - Unity] ExitCode: 2 Duration: 0s53ms
    2. 53829: [2022-12-05T09:26:23Z - Unity] tundra: error: Unexpected stdin
    3. 53830: [2022-12-05T09:26:23Z - Unity] ERROR: Backend produced unparsable log entry
    Update: it fixed by itself
     
    Last edited: Dec 6, 2022
    Revolter, Dec 5, 2022
    #1

  2. KrisGayClipwire

    KrisGayClipwire

    Joined:
    May 26, 2021
    Posts:
    41
    Yes we are also have this issue. It seems to be related to firebase 10.2.0 for us.
     
    KrisGayClipwire, Dec 6, 2022
    #2

  3. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    I believe there is a known bug for the latest version of Unity 2021.3.15f1 and Firebase. If you are using Latest 2021 or Latest 2021.3.X then try setting your Unity version to 2021.3.14f1 to see if this resolves the issue.
     
    Benjamin-Gooding, Dec 6, 2022
    #3

  4. JamesA24

    JamesA24

    Joined:
    Sep 6, 2018
    Posts:
    28
    This doesn't seem specific to Unity 2021.3.15f1. We're doing cloud builds off Unity 2021.3.10f1 instead and we also get those errors using Firebase 10.2.0 for IOS. We've rolled back to Firebase 10.0.0 in the mean time.
     
    JamesA24, Dec 6, 2022
    #4

  5. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    216
    On Firebase 10.0.1 builds fail just sometimes
     
    Revolter, Dec 7, 2022
    #5

  6. KrisGayClipwire

    KrisGayClipwire

    Joined:
    May 26, 2021
    Posts:
    41
    Yeah so I had some test builds that accidentally got set up to run automatically over the weekend. One of them succeeded, one failed and then the one this morning succeeded as well all using the EXACT same settings (since they were set to auto-build).

    At the same time our development build (also set to autobuild) failed twice, and then succeeded once. Again with the exact same git reference, no configuration changes since nobody was working on it on the weekend.

    Is it possible that there is a configuration or something that is not set up correctly so that the machines which get assigned to make builds might be broken by it only sometimes?
     
    KrisGayClipwire, Dec 12, 2022
    #6