I forgot to mention, but we released a new version to prevent this issue and pushed it out to our autoupdater: