This issue has now been resolved in the new 1.2.0a package. Apologies for this fix taking this long to release, many other priorities have taken over during the past couple months, both project and personal wise.
