As this has been resolved, and the permenant fix was released in Patch 1.3.0, this ticket is now closed.

Thank you,