You must log in or register to comment.
Finally! And it seems it’s the 2024.6.2 with the actual fix (2024.6.0 seems to have promised a fix that didn’t cover all cases),
Version 2024.6.2 does not include the final fix for this issue. We are still completing our internal testing, but we plan to submit another release to the store later this week as soon as it is verified.
from the github issue
Glad to hear this is being worked on, thanks for sharing this. I assumed it was related to my config and was putting off looking into it further.