cdflasdkesalkjfkdfkjsdajfd

I just installed Revolut on my new device and got the same error. Not able to use Revolut. But it still works on my previous device.

I wrote them a 1* review and communicated with them, got the very same copy-pasted response. Time to look for an alternative it seems :(

      Does anybody know any EU alternatives? I'm mainly interested in creating many virtual cards and automatic top-up from a card. Thanks.

        Aquathing Does anybody know any EU alternatives?

        It's not just a question of the alternative. Rather, whether this alternative runs on alternative ROMs, and if so, for how long.
        It can't be in everyone's interest to change banks or providers every few weeks.
        Therefore, the idea must be not to look for another bank or provider as an alternative, but to consider whether the alternative in such a use case might not be stock Android. As long as there is no solution from Google or quick hack from GOS and more and more apps have problems.
        At the very least, this must be a legitimate thought experiment and not immediately dismissed.

            AlphaElwedritsch Pretty sure that most people will be able to make up their own mind on whether to return to stock PixelOS or not.

              SilverCat38 You feel right I'm afraid. Apparently the older version which was working has been blocked, forcing to update. And here is what Revolut just replied to me on Playstore:

              Hi there! At the moment, GrapheneOS is not supported and if we do have any plans to introduce this anytime, we'll be sharing the news via our official social media channels.

                  hungrily6100 My first email said:

                  I send them pretty same text and got this reply:

                  Hello,

                  Hope you are doing well!

                  Thank you for sharing with me your feedback. I will definitely pass it to the development team! Our team greatly appreciates your suggestion, and we will pass it on to our development team. We take the opinion of each user very seriously as we always try to improve our app taking into account the feedback we get.

                  Appreciate your understanding!

                  Best Regards,
                  Zee
                  Revolut Customer Support

                  I also cancelled my Premium subscription with Revolut and stated the issue with GrapheneOS as reason.

                    Different experience here. I have asked support what's the real story here, and they told me they are working on a fix.
                    Me: "Some users have asked Revolut's support, and some agents
                    said that they are working on fixing this, while others have
                    said there are no plans"
                    Them: "Be assured I would like to share that your feedback matters
                    the most to us and I am forwarding this feedback and be
                    assured we are working on it."
                    Me: "So can you confirm that there is a fix in progress, or are you
                    just saying that the feedback will be taken into acocunt?"
                    Them: "Yes, we are working on it"

                    I would also like to point out that they use AI for the first replies, I spotted that and asked to talk to a real agent.
                    I'm not sure if the same is happening via email, and if the replies saying that there is no fix planned are from the AI.

                    SilverCat38 revolut web is a highly limited ui. you cannot view disposable cards and/or view the data of your virtual cards, even if you enable full access (you need to be logged into the app to do it).

                        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...