Just updated to latest and it's partially fixed. I've sent over an email with the exact error details and how I resolved them locally. Thanks!
