We released a version shortly after where, at least when I tested it, didn't had this bug. I am not sure if you got the previous one, or is still having this problem. If the problem is recurring I have no clue of what it is since it works on my end now.