Search Issue Tracker

Fixed

Fixed in 2021.3.30f1, 2022.3.6f1, 2023.1.5f1, 2023.2.0a23, 2023.3.0a1, 2024.1.0a1

Votes

8

Found in

2021.3.11f1

2022.3.3f1

2023.1.0b20

2023.2.0a18

2023.3.0a1

2024.1.0a1

Issue ID

UUM-17689

Regression

No

Build would sometimes fail with Tundra build failed error

--

-

Reproduction steps:

# Open the “TundraFail” project
# Click File → Build And Run

Expected result: Build successes
Actual result: Build fails, error in the Console

Reproducible with: 2021.3.9f1, 2021.3.11f1
Could not test with: 2020.3.41f1, 2021.3.12f1, 2022.1.21f1, 2022.2.0b13, 2023.1.0a16 (behavior is intermittent, takes a lot of time to reproduce)

Reproduced on: macOS Monterey 12.0.1

Note: if the issue is not reproducible, repeat step 2 until it reproduces

Error:
CommandLine
"/Applications/Unity/Hub/Editor/2021.3.11f1/Unity.app/Contents/Tools/netcorerun/netcorerun" "/Applications/Unity/Hub/Editor/2021.3.11f1/Unity.app/Contents/Tools/ScriptUpdater/ApiUpdater.MovedFromExtractor.exe" "Library/Bee/artifacts/200b0aE.dag/Unity.Services.Core.Environments.dll.mvfrm" "@Library/Bee/artifacts/200b0aE.dag/Unity.Services.Core.Environments.dll.mvfrm.rsp"
ExitCode 132
*** Tundra build failed (17.55 seconds), 1640 items updated, 1641 evaluated

Comments (1)

  1. chaehyeok

    Nov 15, 2022 09:12

    This also happens on Unity2021.3.2f1, Windows platform.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.