This issue has definitely been reported to the dev team, and will be resolved in a future patch update.


I work here