Yes, it would be harmful if WhatsApp bans GrapheneOS. But personally – unless several more people are able to reproduce this eventually – it's not clear to me that this problem is due to an OS integrity check. The fact that a WhatsApp customer support representative – and their documentation – says that "custom ROMs" are not "supported", I think is equally likely to mean that WhatsApp simply does not provide customer/user support for people running aftermarket operating systems. It makes sense then that the CSR is following internal instructions and dismissing OP's support request.
WhatsApp "You need the official WhatsApp to log in".
- Edited
I did it the other way around: I banned WhatsApp. It's one of the apps I strictly avoid because of data misuse.
I installed GrapheneOS for additional security. Isn't it absurd to continue running the very apps on GrapheneOS that are the worst data octopuses?
With using GOS comes the task to find alternatives to all those apps.
Dan-cer Agree, but I am not able to convince the school/teachers to switch to signal. The alternative they offer as parent-teacher communication is facebook messenger. Ehh.
emilycestmoi I'd download some older whatsapp apk and try that.. I am not encouraging you to do that because you have to download it from "somewhere". I had to do it about a year ago, there was a buggy whatsapp release that was causing extreme battery drain on my cellphone.
Pixel 9 Pro
Set up a clean test user profile, installed sandboxed google play first in the app and gave it notification permissions.
Installed WhatsApp. It allowed the creation of an account without issue. The one thing I couldn't do was set up a Passkey. I did not try linking to an established account. This was a test with a disposable Sim card in another device. The test profile had no phone or SMS permissions.
Dan-cer could not agree more.
Dan-cer Isn't it absurd to continue running the very apps on GrapheneOS that are the worst data octopuses?
It is not absurd at all. It's your personal choice to avoid these types of app.
Other people can't live without mainstream apps like social media, WhatsApp and other highly invasive apps. It makes more sense to use these invasive apps on GrapheneOS rather than any other OS due to both the security and privacy advantages.
Obviously you will benefit from security hardening no matter what apps you use, but you will benefit more from the privacy features of the OS when you use invasive apps rather than apps that respect your privacy. As much has been said by the official GrapheneOS team so they share the same view.
andrej567 well, you have an documented excuse not to use it, don't you?
Unless the teacher shows you how to make it work.
Just don't tell her it's custom rom.
15 days later
Another user reported the same issue on Matrix. Suddenly logged out of WhatsApp account even though it was working properly before. WhatsApp was installed from the Play Store. Was not an issue with their number as logging in on a device that passes Play Integrity worked. Seems like WhatsApp is gradually rolling out Play Integrity checks. Very unfortunate.
DeletedUser88 Seems like WhatsApp is gradually rolling out Play Integrity checks. Very unfortunate.
Did they provide system logs so that this assumption can be ascertained? And does anyone here know how to determine the usage of the Play Integrity API by apps by looking at a system log?
- Edited
fid02 Did they provide system logs so that this assumption can be ascertained?
No. Although, I don't see any other reason there would be issues logging into WhatsApp on an OS that doesn't pass Play Integrity while there are no issues on an OS that does.
fid02 And does anyone here know how to determine the usage of the Play Integrity API by apps by looking at a system log?
GrapheneOS said they'll be adding a notification to inform users about this.
DeletedUser88 No but I don't see why else the user would have issues logging in on a device that doesn't pass Play Integrity but has no issues when logging in on a device that does.
Was the state of their device determined? Relevant information would include whether the bootloader was locked or unlocked, and whether OEM unlocking was enabled or disabled.
fid02 Bootloader locked, developer options and OEM unlocking disabled.
emilycestmoi Have you ever used a third party WhatsApp client on any of your phone numbers?
4 days later
I've got the same issue on iode OS when registering a new number. Maybe this testing could help someone:
https://community.iode.tech/t/any-help-getting-whatsapp-working-on-fp5-iodeos-5-8/5141/8
kireFPX I've got the same issue on iode OS when registering a new number. Maybe this testing could help someone:
https://community.iode.tech/t/any-help-getting-whatsapp-working-on-fp5-iodeos-5-8/5141/8
Although you are not running GrapheneOS, to have some context it would be very interesting if you could answer the following:
- On your iode OS, is your bootloader locked or unlocked?
- On your iode OS, is OEM Unlocking enabled or disabled?
- On your iode OS, are Developer options enabled or disabled?
- Have you ever used a third party WhatsApp client on any of your phone numbers?
fid02
Yes sure:
In my post I already did a lot of testing: "I’ve relocked the bootloader, disabled OEM unlocking, disabled iodeBlocker disabled developer options all together [...]"
and i did never use any third part WhatsApp client. I know however, that WhatsApp is unhappy on how old my phone is since ive got a warning that whatsapp will be disabled for me in may. Through the "contact us" button im also certain that they detected my Jailbreak (they refuse any Help cause of it).
I tried to register to a diffrent phone number from my iode phone, which worked. So its dependent on my WA Account/my old phone. But IodeOS/Custom roms are still the isssue, since registering an old samsung to my phonenumber worked without issue.
I am guessing: Since my account has been flagged somehow (Jailbreak, old ios version, blocked WA updated even though im now on the newest version) whatsapp does some extra checks when registering a new phone to that number. The stock samsung one clears them, while the Custom Rom (IodeOS) fails them. This then triggers the Error we have been seeing.
in the replies to my post ive also checked the difference in play integrity/SafetyNet. SefetyNet checks pass the same way on both phones. Basic play integrity passes and strong Integrity fails on both phones.
But the custom rom phone fails device integrity while the stock samsung one passes.
please let me know if any more tests would be helpfull, since im sadly planing to revert to stock android
- Edited
fid02
I am now on FairphoneOS but unable to relock my bootloader due to patchlevel.
Only basic play integrity checks, "device" and "strong" fail. YASNAC Fails on "CTS" with the recommandation to lock the bootloader.
OEM unlocking is enabled (obviously), usb debugging is enabled and active, same for developer options.
BUT WhatsApp sign up works with my (likely) flagged number.
I hope this information can help some dev in understanding whats going on. We all dislike Whatsapp, but getting it to run on degoogled devices is kind of important in our current society.
Im willing to test more things even with a fresh install till a new FairphoneOS updates releases.
Thank you
24 days later
I'm experiencing the same with a fresh new install on pixel 7 and new SIM. Installed from at store, it first worked and after sending some messages I got banned. 24hs later the ban was removed (I received a notification), but couldn't login anymore, no mater what I try, I always get the "unofficial app" message. A big problem because my family and friends all use whatsapp.