I wonder if there is anything that can be done from the Graphene project perspective to solve these issues. I feel like there is a new app (typically financial) popping up every couple days that has this issue of not working on Graphene.
At some point in the not too distant future, I could see a Graphene phone just becoming a secondary device or for people who do not want to use their phone for financial purposes
Same bank. But I think all banks use the same core app of Twint, just adding their corporate identity (logo) to it.
At some point in the not too distant future, I could see a Graphene phone just becoming a secondary device or for people who do not want to use their phone for financial purposes
Indeed. And this is a pity, because you should use a secure device (like a GOS one) to do financial (and therefore sensitive) stuff.
CS has not released a new version yet so it is still working (play services installed but not signed in, using a secondary profile). Will check once an update is available.
treenutz68 This is something in GrapheneOS I still have not understood: GrapheneOS claims that the user has control which app can exchange data with others (typically Google Play apps). But there is no such permission on the Twint App (neither granted nor forbidden). Still the app gets a reply from PlayStore that you are not logged in and refuses to work.
If there is such a data exchange GrapheneOS should always answer "connected" to apps that question the Play Store status. Similar as the location can be redirected and faked.
schweizer I think this post partially answers your question: https://discuss.grapheneos.org/d/18749-aurora-problem/14
schweizer GrapheneOS claims that the user has control which app can exchange data with others
Can you reference this claim? I know it's been mentioned that they would like to implement app communication scopes but I'm sure we're a ways out from that.
There are a number of reasons why it's not in GrapheneOS' best interest to simply "spoof" checks like this. Including, but not limited to it giving a bad image of GrapheneOS to the uninformed which will make app compatibility even more difficult.
GrouchyGrape Here they write "apps within the same profile can communicate with each other with mutual consent". This is not true. But that's offtopic here.
schweizer but that is true, that's the issue being discussed in this thread. Apps are communicating with each other with mutual consent, exactly as intended.
I'm suspecting there's a language barrier going on? Forgive me if I'm incorrect in thinking this.
fyi, i also installed GrapheneOS a few weeks ago and wanted to install UBS Twint. Didn't work (the App was flashing strangely and touch didn't really work). I'm now using Twint Prepaid without any issues. You can charge it up through your bank (until 200 CHF will be immediately be topped up, the rest is after the transfer is complete). So if that is an alternative for you.. Limits are just not as high as in the native Twintapp of your Bank. But i can live with it.
FYI, I manage to install and make Twint works in the Private Space, where I enabled GSF and logued with a fake google account for Play Store.
I got a reply from Migros Bank. They do not develop Twint themselves and forwarded the complaint to that company.
GrouchyGrape
Well, being a non native English speaker the term "mutual consent" is not what I would use to describe things that happen against my will. I am convinced that apps can at least detect the presence of other apps since I had a case where a banking app refused to work because an other app was detected.
And I ask myself what is the "intention" of forcing an ID that is tied to a passport being transmitted to Google. This is usually a KYC thing. But as a Twint customer you are already identified against your bank. So there is no good reason to additionally send identity to Google unless they get some kickbacks from them. Or another crummy deal. Or incompetence.
schweizer gotcha, that makes more sense. If you understand the phrase "mutual respect", you understand that it means there are two parties that respect each other with no other parties involved. "Mutual consent" in this setting is very similar. The two parties are simply two apps that are mutually consenting to communicate with each other with no other party (being you) involved. It's not mutual consent between you and the two apps, just the apps by themselves.
There are plenty of legitimate reasons for this that I'm totally cool with. However, there are obviously times that I'd like this restricted. Thankfully, the GOS team is working on implementing app communication scopes to mitigate this.
For information Twint still works for me for BCV.
I had a friend that has Migros Bank and a month ago he wrote to me saying that it wasn't working for him anymore. Seems to be a Twint Migros specific thing.
mrn CS version is also still working after update to 2.19.29.0 (play services installed but not signed in, using the app on a secondary profile).
mrn good to know! I have it installed because of push services for this and other finance apps.
The newest version of MB Twint works without a google account again. Problem solved.
I have not tested if Playstore is required at all because I need it for other apps.
