Search Issue Tracker

Active

Under Consideration for 6000.3.X, 6000.4.X

Votes

0

Found in

6000.2.15f1

6000.3.0f1

6000.4.0a5

Issue ID

UUM-129147

Regression

No

Crash on UnityEngine::Analytics::SceneInfoUpdater::EditorDidOpenSceneForBuild when building a specific project

-

How to reproduce:
1. Open the attached “IN-124052” project
2. Navigate to File > Build Profiles
3. Click the “Build and Run” button in the bottom right
4. Observe the crash

Reproducible with: 6000.2.0b2 (d4c40f50eb81), 6000.2.15f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1
Not reproducible with: 6000.5.0a2 (build fails but does not crash)
Could not test with: 6000.0.63f1, 6000.2.0b1 (d17678da8412) (could not solve errors from downgrading)

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Notes:
- If step 2 is completed as: File > Build and Run, a different crash can occur
- The project will build successfully after the Assets or Project Settings folder is deleted
- The build will fail but not crash after the Player settings are reset in the Project Settings

First few lines of the stack trace:
0x00007FFE91B05050 (Unity) UnityEngine::Analytics::SceneInfoUpdater::EditorDidOpenSceneForBuild
0x00007FFE8FB53BC2 (Unity) CallbackArray1<GameObject & __ptr64>::Invoke
0x00007FFE91433DF6 (Unity) EditorSceneManager::OpenSceneForBuild
0x00007FFE91F8C521 (Unity) BuildCopyGameScene
0x00007FFE91F8FBF8 (Unity) BuildPlayerData

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.