@User can you please open an issue on github with your stack trace from earlier? I've seen that issue before and know where it's coming from. It should be a simple fix, but if we dont put a catch in, this will probably occur pretty frequently.