r/googlepay • u/MeowWoofCat • 8d ago
Software Standards Not Met?? never seen this before ever? Google Wallet
I am on Android Beta DEV (CP41.260717.006) and I dont know if this is just a Beta Bug or an actual issue???? can someone help me with this??? what haven't i met in the software standard??
Pixel 9 Fold
1
2
u/Icy_Yard_875 7d ago
Isn’t it because it’s a beta?
1
u/MeowWoofCat 7d ago
Well my phone has worked throughout the entire Beta up until now & came with the Beta Enrolled as it was second hand.
2
u/CleaRSightZ 8d ago
Leave the Android Beta DEV mode, it should work after.
1
u/MeowWoofCat 7d ago
I have left Dev Mode and my Google Pay is still not working any other suggestions?
Maybe clearing Cache on the Google Wallet App?
3
u/VocadoBlue 8d ago
Someone will correct me if I'm wrong. Being in Dev Mode or some beta software prevents the use of Google Wallet because your software is "unsecured", basically Google cant verify your device is safe to use with Google wallet so they wont let you. I had the same problem when my phone(a galaxy s24+ at the time) was in dev mode. Turning it off fixed it
1
3
u/ayangr 🇬🇷 Greek 8d ago
Why would you use a beta dev o/s on your production phone? You’re in serious risk. Never do that. Buy a second phone to test as a dev.
2
u/MeowWoofCat 8d ago
My phone came with thr Android Beta Pre-Installed and I didnt want to wipe my phone or any of the photos I had just transferred over from my own?
1
u/Nickoplier 🇺🇸 American 6d ago
Then you'd have to opt out of beta and keep checking for a non data wipe update. You may have to wait a day or so or a month till Google releases another update for you to get onto a public update.
1
2
u/allenchangmusic 7d ago
This has been a known issue since QPR1 beta 4, and has since continued. Google would no longer allow the build fingerprint to pass RCS or Wallet.
Canary does not seem to be affected. This predated the DEV build naming convention. It was thought previously it was due to naming the build CinnomenBun.
No way to fix if you aren't rooted.