Hey TacticianDaraen, thanks for reporting these in! We will keep an eye out for this error. There is a major update coming out in a few days (v1.6.0) which may have already taken care of this issue. Once that update is available, please let us know if the issue persists in which case we can spend some time to investigate the bug and issue a patch to fix it.