We're working on a fix for this bug. The error messages should be gone shortly.