This looks like it's been fixed on Google's side. Please try again and let me know. Thanks!