Let me know if that bug is still present on V0.6.3.1
I haven't been getting the error messages anymore in the most recent build, so looks like you got it!
