Comment by crazygringo

A bunch of comments here are assuming this is something intentional on Google's part.

Simply from the error message alone, it's obvious that this is a bug. As well as from how easy the workaround is.

Google might do many things wrong intentionally, but I see zero evidence this is one of them. Just a bug, folks.