UniTask.WaitUntil works in Editor but not Build

[Moddingdudes]

I'm patching a simple issue in my code where a Gamemode instance is null due to it being instantiated after it is needed. It's not necessary to refactor this entire setup for a simple issue, so I wanted to run the following:

await UniTask.WaitUntil(() => GameManager.singleton.Gamemode != null);

(Yes I used singletons in this project, I regret it but the show must go on)

It works perfectly in the Editor, but when I build it, it seems to have some sort of internal UniTask issue. I've verified that on the build, the singleton value is set properly almost immediately after the error. The error dump is:

NullReferenceException: Object reference not set to an instance of an object
  at Cysharp.Threading.Tasks.PlayerLoopHelper.AddAction (Cysharp.Threading.Tasks.PlayerLoopTiming timing, Cysharp.Threading.Tasks.IPlayerLoopItem action) [0x00001] in .\Library\PackageCache\com.cysharp.unitask@64f7eec4e9\Runtime\PlayerLoopHelper.cs:494 
  at Cysharp.Threading.Tasks.UniTask+WaitUntilPromise.Create (System.Func`1[TResult] predicate, Cysharp.Threading.Tasks.PlayerLoopTiming timing, System.Threading.CancellationToken cancellationToken, System.Int16& token) [0x00040] in .\Library\PackageCache\com.cysharp.unitask@64f7eec4e9\Runtime\UniTask.WaitUntil.cs:75 
  at Cysharp.Threading.Tasks.UniTask.WaitUntil (System.Func`1[TResult] predicate, Cysharp.Threading.Tasks.PlayerLoopTiming timing, System.Threading.CancellationToken cancellationToken) [0x00001] in .\Library\PackageCache\com.cysharp.unitask@64f7eec4e9\Runtime\UniTask.WaitUntil.cs:14 
  at GamePlayer.OnStartServer () [0x0007a] in D:\Repos\Unity3D\Chump Co\Assets\Scripts\GamePlayer.cs:141 
  at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in <787acc3c9a4c471ba7d971300105af24>:0 
  at UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () [0x00002] in C:\build\output\unity\unity\Runtime\Export\Scripting\UnitySynchronizationContext.cs:153 
  at UnityEngine.UnitySynchronizationContext.Exec () [0x0005d] in C:\build\output\unity\unity\Runtime\Export\Scripting\UnitySynchronizationContext.cs:83 
  at UnityEngine.UnitySynchronizationContext.ExecuteTasks () [0x00014] in C:\build\output\unity\unity\Runtime\Export\Scripting\UnitySynchronizationContext.cs:107 

(Filename: ./Library/PackageCache/com.cysharp.unitask@64f7eec4e9/Runtime/PlayerLoopHelper.cs Line: 494)

Not too sure what would cause this? It's just a predicate so I could be overlooking something super simple. Thanks!

[Moddingdudes]

Not sure why this fixed it, probably a Unity bug, but I changed it from the latest version in the Package Manager via Git, to just the unitypackage latest version