Thank you for reporting this bug, which I could verify in the meantime.
The problem was fixed in a new build (v4.70.472), which has been released an hour ago.
The upgrade of installations of the previous build (v4.70.471) to the new build (v4.70.472) is supported.
-Franz