Hey there,
This issue is now fixed with Update 2.6.
We’ll proceed to close this thread. Thank you for the feedback provided those of you who did it in a constructive way.
If the issue still persists after this update, please feel free to send us a new report.