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"
Revolut mobile finance - not supported on devices with custom firmware problem
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.
can you try with revolut web? It should work in a browser
https://app.revolut.com/
- Edited
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).
cdflasdkesalkjfkdfkjsdajfd that sucks, I use revolut daily, hopefully they allow custom roms. I might use a stock os on another phone just for revolut (worst case scenario)
SilverCat38 i don't want to use other device for revolut access. If this situation isn't solved in 1-2 weeks I will close the account and say goodbye to revolut
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.
- Edited
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
- Edited
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?
nat interesting, @GrapheneOS
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...
nat What about edit the APK to remove the DexProtector "integrity" API call then resign the app?
nat You might be onto something here. I have had a look at the logs after installing the app in my work profile (cloned via Shelter), and I do see some similar errors (asking for device_state, ro.debuggable), here's the full logcat of the revolut app: https://gist.github.com/Aquathing/c55de773095d678f464c2ea5a2b29ceb
cdflasdkesalkjfkdfkjsdajfd I assume she searched internally and this is what was presented to her.
I'm not a Revolut user, but I do not subscribe to this Monopoly like approach.
I downloaded the app, checked that it really said that it wouldn't work on my device, and I gave them 1* review on Play.
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.
- Edited
gOS build 2024120400, revolut 10.52.2, pixel6a is working for me.
(play store install)
Update GOS / Revolut to latest version's and report after that, otherwise is not concludent.
spamrisku2jqqrfh the issue is login into the app. The app, if you're already logged in, is working well...
Try logout then login again: you cannot!