are you still getting the error? this happens from time to time and we have to fix it on our end. rest assured, we do have a future fix for this in a later version.