Search Issue Tracker

Fixed

Fixed in 6000.6.0a2

Under Consideration for 6000.5.X

Votes

0

Found in

6000.5.0a4

6000.6.0a1

Issue ID

UUM-130715

Regression

Yes

Test Runner fails to start the Player tests when Build Profiles window is opened

Content Build

-

How to reproduce:
1. Open the attached project "TestRunner"
2. Open the Build Profiles and keep it opened
3. Open the Test Runner (Window -> General -> Test Runner) -> Player 
4. Click "Run All" and observe the results

Expected results: Tests are executed
Actual results: Test Runner fails to launch the tests

Reproducible with: 6000.5.0a1, 6000.5.0a3
Not reproducible with: 6000.4.0a3. 6000.3.0b2
Can't test with: 6000.0.64f1, 6000.2.2f1 (No Player tests)

Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested

First lines or errors:
- InvalidOperationException: The operation is not possible when moved past all properties (Next returned false)
UnityEditor.SerializedProperty.Verify (UnityEditor.SerializedProperty+VerifyFlags verifyFlags) (at /Users/bokken/build/output/unity/unity/Editor/Mono/SerializedProperty.bindings.cs:532)
- Player build failed
UnityEditor.EditorApplication:Internal_CallUpdateFunctions () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorApplication.cs:403)
-TestLaunchFailedException: Player build failed
UnityEditor.TestTools.TestRunner.PlayerLauncher.Run () (at ./Library/PackageCache/com.unity.test-framework@ba673b29c67e/UnityEditor.TestRunner/TestLaunchers/PlayerLauncher.cs:88)

  1. Resolution Note:

    Fixed in 6000.6.0a2

  2. Resolution Note (fix version 6000.6.0a2):

    Fixed in 6000.6.0a2

Log in to vote on this issue

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.

Latest issues

See all new issues