We shipped an update related to this yesterday - can you test again and see if you’re still receiving an error?