The lastest version is just giving this error…
Returning to version 3.3.1 solved this for now…