This issue should now be fixed in the builds v1.1.1 and later. Pre-release posted here:
Let me know how it works for you.