I have the same issue and exact same error message. This must have happened after a recent update because the plugin used to work fine anf then on day it did not
Will anyone from the support team respond?
