Welcome to the community.
This issue is known. We reported it in the thread for the firmware that caused the issue. Typically, it’s best to try to report beta bugs in the thread the firmware was announced in since that is where the devs will be looking for it. Here they are saying they have it fixed though:
Today they just said the new firmware should be released sometime this week with a fix for it. 