cdflasdkesalkjfkdfkjsdajfd
Unfortunately, I can confirm this:
Now, I can't login into the app even when 10.54
At the end of the login process the app says "update to last version to continue" then no login
cdflasdkesalkjfkdfkjsdajfd
Unfortunately, I can confirm this:
Now, I can't login into the app even when 10.54
At the end of the login process the app says "update to last version to continue" then no login
fid02 check this conversation:
cdflasdkesalkjfkdfkjsdajfd check this conversation:
You made a rude reply to the CSR instead of arguing constructively like most other users in this thread have managed to do. I'm not surprised the CSR replied like they did.
fid02 I'm pretty sure this will not make any difference at the end
Think everyone is just spinning their wheels.
There are approximately 1.4 billion iPhone users and 3.9 billion Android users in the world. There are approximately 300 thousand Graphene OS users. In other words, Graphene OS represents 0.0057% of the smart phone population.
What company that cares about maximizing the returns of their engineering resources would care about less than 1% of 1% of the addressable market? I can see privacy respecting companies caring, but hell, we haven't even been able to convince MySudo (a presumably privacy focused company) to support graphene properly and that was with Michael Bazzell pushing them to do so for years!
treenutz68 Totally agree!
treenutz68 What company that cares about maximizing the returns of their engineering resources would care about less than 1% of 1% of the addressable market?
Worth noting that a lot of GrapheneOS users contacted Starling about this at the time. They stopped blocking GrapheneOS at the end.
That's wonderful news. I wish mysudo was equally as responsive to graphene users needs. I think they've had an open issue around it claiming they would fix it for years. The problems being 1) no notifications without google play services and 2) you need a second stock ios or android device to make initial and subsequent payments
Felt like if a company that literally exists to improve a user's privacy didn't bother helping out graphene users (after acknowledging the issues years ago) then the odds are pretty low most non-privacy friendly companies will care.
Perhaps one note of interest: starling bank has roughly 4 million customers, while Revolut (the company at issue in this thread) has 45 million customers. Perhaps the size has something to do with their flexibility and responsiveness to a limited number of customer complaints?
treenutz68 Perhaps one note of interest: starling bank has roughly 4 million customers, while Revolut (the company at issue in this thread) has 45 million customers. Perhaps the size has something to do with their flexibility and responsiveness to a limited number of customer complaints?
It's only been 7 days since GrapheneOS users first contacted Revolut about this. Unless a flood of users start reporting that Revolut is telling them that "no, GrapheneOS will never be allowed, sorry, this comes directly from our developers", I'm personally not yet inclined to conclude that Revolut is going to ignore this – even if it feels like a lost cause. Might be worth noting that in general developers usually have a ton of things to do, and other "bugs"/problems might be prioritized even if others aren't going to be ignored and might be looked into in the future in spite of only affecting a minority of users. I don't think a week is a lot of time in that context.
Yeah, I had similar hopes for mysudo for a couple years. Fingers crossed Revolut does not disappoint in a similar way!
Yeah, the unfortunate conclusion is to not use an app-only/app-first bank. Use some high street bank that gives you a hardware token or uses SMS codes to authenticate you.
Still a sad development, because I'm sure the whole Play Integrity thing won't stop with banking apps and McDonald's... One day it might even be a requirement to be listed in the Play Store! (though hope springs eternal)
The contents of the email I've received from support team after 1 star rate in Play Store is pretty clear:
Hello, thanks for reaching out to us.
We appreciate your patience.
Our application might not work on phones running MicroG, GrapheneOS or other operating systems and we do not officially support it or conduct any compatibility tests. This means the application may have limited functionality or might not be usable at all. We have no plans to support those systems in the foreseeable future.
Thank you for understanding.
Kind Regards
Teejay
Revolut Customer Support
cdflasdkesalkjfkdfkjsdajfd I have grapheneos. I had your issue a while back.. I managed to solve it by adding google play services with network permissions (for notifications ) and install revolut... everything on the work profile via shelter
SilverCat38 I really doubt it, due to I have tested on my primary device (GrapheneOS) and also in the test device (LineageOS + OpenGapps) and the issue appears on both devices
SilverCat38 You likely signed up and signed in before they started with the blocking in one of the recent releases. It is explained in this thread.
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.