Search Issue Tracker
Fixed
Fixed in 1.5.x
Votes
0
Found in [Package]
1.4.4
1.5.x
Issue ID
LOC-992
Regression
No
Exception raised by WaitForCurrentOperationAsyncOperationBase when Dependency is not valid anymore in Localization 1.4.4
When a {{WaitForCurrentOperationAsyncOperationBase}} has {{InvokeWaitForCompletion}} invoked, the Dependency is waited on, after which the {{Dependency.Status}} is checked. This can cause an exception where {{Dependency.IsValid()}} is false.
{{Attempting to use an invalid operation handle}}
This exception comes from {{AsyncOperationHandle.InternalOp}} where a null value will result in the above message.
We have attempted to reproduce this issue, building to iOS and MacOS, but were unable to. And the customer who is experiencing this issue hasn’t been able to narrow this down either.
The customer worked around this issue by adding a {{Dependency.IsValid()}} check after {{WaitForCompletion}}, but I believe this statement should instead read:
{{if (!Depedency.IsValid() || Dependency.Status == AsyncOperationStatus.Failed)}}
The expected outcome is that the {{WaitForCurrentOperationAsyncOperationBase.InvokeWaitForCompletion}} doesn’t raise an exception and fails gracefully.
Reproducible on according to the Customer: Localization 1.4.4 (2022.3.8f1)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
- [Linux] "Error while reading movie" errors are thrown when opening templates
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
Add comment