0 • Edgar Cervantes / Android Authority co/AAGooglePreferredSource"> Add us as preferred source TL DR An Android 17 update caused some Pixel phones to show a “Phone doesn’t meet security requirements” error in Google Wallet.
What happened
0 • Edgar Cervantes / Android Authority co/AAGooglePreferredSource"> Add us as preferred source TL DR An Android 17 update caused some Pixel phones to show a “Phone doesn’t meet security requirements” error in Google Wallet. The bug blocked contactless payments and card enrollment, even though the affected devices passed Play Integrity checks. Google has rolled out a server-side fix. Users should restart their phone and wait up to 24 hours for it to take effect.
Practical impact for readers
A recent Android 17 release appears to have left some Pixel owners unable to use Google Wallet . Affected devices began showing a “Phone doesn’t meet security requirements” error, removing payment cards and preventing users from adding new ones. The good news is that Google has now rolled out a fix, although it may take some time before affected devices recover. A fix is rolling out now should be explained through that lens before any broad claim is made.
Details worth verifying
The issue was particularly confusing because affected phones still passed Play Integrity checks and remained Play Protect certified. User reports on Google’s Pixel support forum, along with several discussions across Reddit’s Google Pixel and Google Wallet subs, showed that Google Wallet refused to process NFC payments even though the devices appeared fully certified. Some users also reported that apps like Too Good To Go were suddenly marked as incompatible.
Who should act or wait
The bug appears to have affected the Pixel 10 most frequently, although some Pixel 9 series owners also reported the problem . Everything from clearing Google Play Services data to factory resetting their phones failed to fix the issue.
What is still unclear
While Google hasn’t publicly explained what caused the issue, a support representative told one affected user that a server-side fix has been deployed . Some users have speculated that the problem was related to backend device attestation, though Google hasn’t confirmed that explanation.
Latest comments
0No comments yet. You can start the conversation.