We're currently working on figuring out the issue, so sorry about that! We wrote some more details in the first devlog post here!
