I can confirm what others have pointed out already. Using an older version does not work anymore as it won't allow you to log in without updating it first. Updating the app will then obviously lock you out with the devices with custom firmware not supported.

I'm as well trying to put a bit of pressure on them through reviews and their support, but I'm slowly starting to consider alternatives to Revolut. I'm hoping they resolve this with a future update.

https://i.imgur.com/sDZSemr.jpeg

This is an agent, not a bot. I asked the bot for a direct agent connection and after 3 more questions they connected me directly to a person.

I'm sorry you're dissatisfied, and I understand this must be frustrating for you. I want to reassure you that your concern has been our top priority from the start. I am fully committed to finding a solution with you. Please also remember that you can raise a formal complaint at any time. Just let me know, and I can guide you through that process if you'd like. Please keep in mind that our resolution will always be in line with our standard policies and procedures

    I'm not risking logging out on my device to confirm that but I heard that Revolut isn't using Play Integrity API but rather DexProtector/Licelus. They have this demo app https://play.google.com/store/apps/details?id=com.dexprotector.detector.envchecks
    I ran it with logcat open and I haven't seen any logs from Play Integrity (not sure what to expect, I remember that SafetyNet would show results in logcat). Perhaps it would be easy to spoof on OS level whatever this thing doesn't like? I can see in logcat stuff like

    12-08 23:28:40.826 22793 22793 I com.dexprotector.detector.envchecks: MMAP_TRYLOCK is supported in uffd errno:2 addr:0x6bd2ddd000 size:4096
12-08 23:28:40.827 22793 22793 I AndroidRuntime: Using default boot image
12-08 23:28:40.827 22793 22793 I AndroidRuntime: Leaving lock profiling enabled
12-08 23:28:40.827 22793 22793 W libc    : Access denied finding property "odsign.verification.success"
12-08 23:28:40.827 22793 22793 W libc    : Access denied finding property "ro.debuggable"
12-08 23:28:40.828 22793 22793 E cutils-trace: Error opening trace file: No such file or directory (2)
    12-08 23:28:40.940 22793 22793 W libc    : Access denied finding property "ro.product.name_for_attestation"
12-08 23:28:40.940 22793 22793 W libc    : Access denied finding property "ro.product.device_for_attestation"
12-08 23:28:40.940 22793 22793 W libc    : Access denied finding property "ro.product.manufacturer_for_attestation"
12-08 23:28:40.933 22793 22793 W main    : type=1400 audit(0.0:106100): avc:  denied  { read } for  name="u:object_r:build_attestation_prop:s0" dev="tmpfs" ino=181 scontext=u:r:untrusted_app:s0:c18,c257,c512,c768 tcontext=u:object_r:build_attestation_prop:s0 tclass=file permissive=0 app=com.dexprotector.detector.envchecks
12-08 23:28:40.940 22793 22793 W libc    : Access denied finding property "ro.product.model_for_attestation"
12-08 23:28:40.933 22793 22793 W main    : type=1400 audit(0.0:106101): avc:  denied  { read } for  name="u:object_r:build_attestation_prop:s0" dev="tmpfs" ino=181 scontext=u:r:untrusted_app:s0:c18,c257,c512,c768 tcontext=u:object_r:build_attestation_prop:s0 tclass=file permissive=0 app=com.dexprotector.detector.envchecks
12-08 23:28:40.940 22793 22793 W libc    : Access denied finding property "ro.debuggable"
12-08 23:28:40.933 22793 22793 W main    : type=1400 audit(0.0:106102): avc:  denied  { read } for  name="u:object_r:build_attestation_prop:s0" dev="tmpfs" ino=181 scontext=u:r:untrusted_app:s0:c18,c257,c512,c768 tcontext=u:object_r:build_attestation_prop:s0 tclass=file permissive=0 app=com.dexprotector.detector.envchecks
12-08 23:28:40.933 22793 22793 W main    : type=1400 audit(0.0:106103): avc:  denied  { read } for  name="u:object_r:build_attestation_prop:s0" dev="tmpfs" ino=181 scontext=u:r:untrusted_app:s0:c18,c257,c512,c768 tcontext=u:object_r:build_attestation_prop:s0 tclass=file permissive=0 app=com.dexprotector.detector.envchecks
12-08 23:28:40.933 22793 22793 W main    : type=1400 audit(0.0:106104): avc:  denied  { read } for  name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=448 scontext=u:r:untrusted_app:s0:c18,c257,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.dexprotector.detector.envchecks

    Or maybe it would also be possible to make them whitelist GrapheneOS since well... they're not Google?

      Nuttso I don't know if the answer was made by a robot or not, but I'm pretty sure that is a predefined answer: no one will help with this issue...

          Moisture I see Revolut answers on Google Play mention GrapheneOS even if the original user review doesn't contain any reference to it :)

            Just a naive question about this situation. What about filing complaints to the Financial Ombudsman Service and the FCA, for all customers depending on Revolut UK. I don't know about such instances for other countries though. Just mentioning UK as I live in the UK. Because right now, we are locked out of our accounts aren't we? And Revolut UK is FCA regulated.

            Update GOS / Revolut to latest version's and report after that, otherwise is not concludent.

            Hello!

            I am a beta tester and can only write private reviews to the developer of Revolut.

            I wrote my review and got the following reply:

            Dear Play reviewer,

            The following Play review 635045a4-0689-4b3c-b84d-6260229f59fd has been hidden from global view because it was identified through automated internal mechanisms as a violation of our Play Ratings and reviews posting policies:

            Since the last update Revolut does not support the security and privacy oriented Android OS called GrapheneOS. Please add GrapheneOS support using the appropriate hardware attestation API and whitelist GrapheneOS according to the guide: https://grapheneos.org/articles/attestation-compatibility-guide#attestation-compatibility-guide Thank you

            Specifically, Your review contains information that is not relevant to the content, service or experience that you’re reviewing. Reviews must not contain political or social commentary, nor should they include solicitations. . This is a permanent action taken globally across all Play surfaces; however, you may edit or apply for redress options as per the below instructions.

            Ratings and reviews are meant to be helpful and trustworthy, and our policies are in place to help ensure a safe experience for all Play users. Remember, you can always modify and resubmit your review in line with our policies. And here are some general guidelines for writing a good review:

            •Make your reviews useful and informative.
            •Try to include both positives and drawbacks.
            •Keep it readable: check grammar and spelling, and don't use excessive capitalisation and punctuation.
            •Be nice to others.

            If you’ve reviewed the policy and feel that our decision may have been in error, please submit an appeal here. You can also learn about additional redress options that may be available to you here. (Routing ID: YJWF)

            Many thanks,
            Google Play Reviews team

            Could anyone help me figure out what to write to not get flagged or what to write in the appeal?

            Thanks

              Anyways, I've contacted support again, and this time the answer was different:
              Aquatica:
              _I asked the other day about the recent update that prevented GrapheneOS users from using the Revolut app. I was assured that the issue will be fixed, but I see online that some support agents are still saying that GrapheneOS is not going to be supported.

              This OS is based on Android, it's no different from Samsung OneUI, Xiaomi or whatever other OS based on Android.
              The recent update prevents the app from running due to the recent Play Integrity API implementation, which requires the OS to be signed by Google. I was told the team was working on fixing it, but different support channels are saying different things. Can you share some details and if possible an ETA? Thanks._

              Revolut
              I understand your concern about the compatibility of the Revolut app with GrapheneOS and the Play Integrity API. We have already forwarded your feedback to the team, they will surely look into this matter for you.

              Aquatica
              _I understand, but I'm looking for a more in-depth answer.

              A lot of users have reported this to Revolut, and all of them have received different answers, even myself right now. First, I get told that they are working on it, now it's a forwarded feedback. What exacty is going on here?_

              Revolut
              I understand the confusion caused by receiving different responses. Our team is currently reviewing the details and I recommend keeping an eye on official Revolut communications, such as updates on the Revolut website or app store listings, for any announcements regarding app compatibility with different operating systems.

              Aquatica
              No ETAs, right?

              Revolut
              Unfortunately, I don't have any specific ETAs or updates regarding this issue at the moment.

              Aquatica
              _Honestly it's frustrating to get told that I should check social media to find out when I'll be able to use my app without issues.

              If I log out now, I won't be able to login anymore, this is bad._

              Revolut
              I understand your frustration, and I apologize for the inconvenience. Your feedback is valuable, and I'll ensure it's passed on to the relevant teams. Thank you for your patience.

              I also wrote a negative review after this (and rated the support experience the lowest score), but have yet to receive a reply.

              • nat likes this.

              The idea that a banking app can block a certain group of it users from access to most of its services is a serious issue.

              I am glad to see that the community is coming together to work against such a change. I hope that this issue will be overcome quickly and I that we can get as many people in contact with their support team as possible.