Hi @AngelBRz and thank you for bringing this issue to our attention.
We are aware of this and the team has managed to fix the issue in an upcoming update.