This bug has been resolved. Please contact support@schemaapp.com if you are running into this again. Read more about how this was solved.