Thanks, for the report. We've managed to see this error sometimes now too and are looking to fix it in GB Studio 3.0.1 soon.
