Code is executed twice in a Coroutine when "WaitUntil(() => Input.GetKeyDown())" is used with "while(true)"

Unity: Scripting Runtime

sw-unity-6-1

Third Party Issue

6.2.X

6.1.X

6.0.X

2022.3.X

The user code is actually to blame here as the second WaitUntil call happens within the same frame as the one that got unblocked by the key press. Luckilly it seems WaitUntil today always wait for at least one frame so it does not end up with an infinite loop, but that is what I expected by looking at the code: within the same frame, Input.GetKeyDown(KeyCode.F) will always return true.

How to reproduce:
1. Open the "ReportingBugs.zip" project
2. Open the "WaitUntilScene" Scene
3. Enter Play Mode
4. Press the "F" key on your keyboard
5. Observe the Hierarchy

Expected result: One "Cube (Clone)" GameObject is instantiated
Actual result: Two "Cube (Clone)" GameObjects are instantiated

Reproducible in: 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3

Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested

Code is executed twice in a Coroutine when "WaitUntil(() => Input.GetKeyDown())" is used with "while(true)"

Unity: Scripting Runtime

Third Party Issue

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Code is executed twice in a Coroutine when "WaitUntil(() => Input.GetKeyDown())" is used with "while(true)"

Unity: Scripting Runtime

Statuses

Third Party Issue

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?