The latest version was updated July 19th 2025, and should have that fixed. That's what I'm seeing on my side
sorry I took the timestamp from the development log instead of the more Information area where I read: Jul 19, 2025.
Still, the error is in there in my downloaded version.
