Hey! Thanks for letting me know. We are already aware of the issue and we are working on resolving it. It's got a problem to do with the new 1.2 update.
