I hope the fix lands on b9, but seeing that the b9 also has the same bug according to the issuetracker, I guess I have to wait till b10 or is there still a hope for a fix to be landed on b9? (since b9 has not yet been publicly released.)
Thanks for the bug report and for sharing the information here @castor76 . This is a high priority issue and currently being investigated. We don’t have an ETA for a fix yet. However, both b9 and b10 have already been cut and are currently tested internally before being released, so the earliest possible version with a fix would be b11 if the issue ends up being on the Editor side. It’s a different story in case the fix will land on the URP package side.