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.

    4 days later

    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

      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.

      Install pixelOS and see if it's getting better

      Just wanted to add that WhatsApp used Play Integrity while I was sleeping. The app is still working as of now.

        This morning i received this new GOS-notification that WhatsApp had used the Google Play Integrity API.
        My GOS P7a has Play services installed, I am on a owner first user profile and WhatsApp is installed from Google Playstore.
        WhatsApp is (still) functional. No warning message from WhatsApp (yet).

          Aquathing Same here. Installed from Play Store since day one, has always worked fine. I also got the Play integrity notification during the night. Working ok for now.

          Stephan-P WhatsApp is (still) functional. No warning message from WhatsApp (yet).

          They are probably using it to gauge the availability and/or as part of an anti-spam strategy, hope they don't start enforcing it. If they do, GrapheneOS is toast, but I don't think they would. Whatsapp has always had huge backwards compatibility (works up to Android 5) and enforcing Play Integrity is at odds with it right now.

          • Edited

          Been getting the "unofficial app" message for a few months now. I don't use WhatsApp often, but I need it for talking with family overseas sometimes. I installed the version from the Play Store and from the WhatsApp website, and it's the same result with the error message.

          My partner has it on their phone with GOS, but they're not getting any errors. I am scared that it will come up and lock them out of their chats. Wondering if I need to put them back in the stock PixelOS just to be safe?

          If there is anything I can do to help in testing this, please let me know.

          9 days later

          Hey all, just wanted to add to this as well as I just started getting this error.
          Working great until I changed my phone number.
          Worked fine with new number for about 24 hours then got 'banned' and couldn't log in.
          When I got 'unbanned' and tried to log back in went to the "You need the official WhatsApp to login" screen when it got to sending the 2FA code to new number.
          Used secondary Pixel 6 phone with stock OS, no problem with logging in with new number.
          Factory reset Graphene, same error -- no change.
          Tried my old number (I'm running 2 sims) it WORKED.

          So for my experience it is bricking or erroring out ONLY when using the new number I changed too, I can log in with old number on same Graphene OS / WhatsApp installed....

          Hope this helps...

          Quick update. In Whats App running fine with the old number I tried add account with the new number. Same issue get the 'Unofficial App' BS.

          Curious if the workaround would be to 'Add Account' instead of going through the changing number via WhatsApp.

          12 days later

          Just want to say that my experience is nearly identical to other people in this thread. Came over to grapheneos with a brand new sim and after inserting the sim, installing WhatsApp and registering my new number everything worked for about a day.Then my account was banned for a few hours before being restored with a message along the lines of "sorry our system mistakingly flagged you". Regardless it made me go through the number confirmation process again and on confirming my number I run into "you must download an official version of WhatsApp" page. Nothing I do fixes this error, uninstalling, reinstalling, increasing permissions etc. I always run into the "official WhatsApp" crap, though it was downloaded from the play store

            12 days later

            Jake same with me, fresh installed of GrapheneOS on 8 pro today with unofficial whatsapp notification.
            Tried installing through aurora, play store and apk directly from website with no luck.
            I can't really move to another chat client because of work and families

            I'm on GrapheneOS with no Google Play Services and I never had an issue.
            I get my app from the official website, through Obtanium.

              rollover5278 As is. I have two numbers, and been enabling a VPN on WhatsApp for years now, which I sometimes connect to different countries in a single day. Never had an issue.