Hi Martinique,
Just to let you know we've reproduced this bug and are working on a fix
This was fixed in the 1.1.17 release.
Simon