I am receiving the same exact error despite that fix. Have you been able to resolve this issue yourself?