Whoops, sorry about that - didn't catch this error in testing.
New builds have just been uploaded that resolve this (v0.6.1-1). Thank you for your patience!
