Hi @Bear,
Thank you for taking the time to report both these issues!
I have been able to reproduce this error on my end, and can confirm it is a bug.
Rest assured, we will have a fix for this as soon as possible.
Indeed, this is a bug.
It seems it is similar to this confirmed bug.
We will also have a fix for this as soon as possible.
Apologies for the inconvenience.