hmmm...
yeah i'm getting this error literally everywhere
That should be fixed in the latest build (v0.0.220d)! Let us know if it is still an issue
