Hi @here! We are glad to inform you that this issue has been officially fixed in Anouncing Play 1.6.0 / Play+ 1.2.0
