The claim is verified by Google's own official support channel, which explicitly addressed the error message as a technical bug rather than a policy change. The report from 9to5Google accurately reflects the official statement provided by the manufacturer.