I believe we have fixed this error as well and have pushed (yet another) update. I apologize for all the updates, but we want to make sure that the issues are fixed and available for widespread use. Please give 0.5.3 a go and let us know if there are any further issues.