Here is another person who cannot activate the Triodos bank App.
When the app will make a photo, to check my identity, i get the error with Google services too.
And unfortunately it won’t be fixed: see my post above with a response from Triodos support
why not move your bank account to another bank ?
And keep Googles nose out of your banking account ?
Because Triodos is one of very few banks that have an effective ethical policy. As their website says
Our banking and financial services are for individuals and organisations who want to change the world for the better. As one of the world’s most sustainable banks, we have over 740,000 customers who are already playing their part in our positive movement.
That is more important to me than whether I can use a mobile phone app rather than web-based internet banking for doing my banking 
I don’t think that the fact the app uses some Google services to allow secure biometric-based login will actually let Google see any details of my bank account
1 Like
I can use the Triodos app without problems.
The only problem is that the app won’t activate by phone.
When i use the camera in the app to check my identity, it will fail and give me an error about Google Services.
So i asked for an identifier to do that.
I have also KNAB, but their you only can banking with the app.
Same solution here. Triodos had deactivated my identifier (automated process) to push me to register via ‘mobile reigstration’. But I couldn’t seem to get passed the step where you need to make a picture. They’ve solved it for me by reactivating my identifier again. Now I can use the mobile app without issues, luckily.
But why would a bank app even need to refer to the Google Play Services? The app is already installed en all it needs to do is to take a picture of a person. Although I’m also having my doubts about a bank taking 3D pictures of their customers (and storing them for further usage)…I think this is very private. I’m not so sure about this development yet.
It doesn’t necessarily have to do with what kind of App it is.
Google is supplying components and services which make life easier for App developers, so this way a lot of Apps simply include dependencies to Google.
2 Likes
I have the same issue with Triodos banking app (Netherlands) on my phone with version 1.9 of /e/OS.
Sent a log to Github page of MicroG also.
1 Like
@Klaas: are you rooted and use LSPoaed Zygisk? Denylist let’s me make use of ALL banking apps without trouble
@Klaas noticed your initial post in dutch and see you found your way. Your bugrep is for the NL version, but the UK appid can very well have different code. Where it fails for triodos uk is at an API call that cannot work with microG. I don’t see that class being called in your triodos NL logcat at all, see github for the rest
I got my problem solved. Thanks very much for your support!!
The solution was: using my digipass, which was de-activated. I asked the bank to re-activate it and with it, I could set up the app.
Still, that doesn´t fix the API Visuals problem.
1 Like
One question left regarding this matter. I really wanted the app to work on my smartphone. I thought: what if I install Google Play Services, set the app, and then remove Google Play Services? I tried, but I am not 100% sure what happened. I believe the system told me: can´t do that. Am I correct? Can one not install Google Play Services on a device with /e/OS? I hope not, because otherwise it wouldn’t be waterproof.
Thanks for the info, AnotherElk! Now I can be sure I haven´t corrupted my device in trying to install it (and remove it afterwards).
If you root your device (install Magisk) all of this trouble is gone anyway.
@Infinity that advice might apply if Safetynet trips, but this is not what happened to the triodos banking Apps what this thread is about (title should be renamed).
They fail on a module call. If the play services vision api module isn’t there to serve its function (face detection), App can’t continue. See linked github issue. Magisk isn’t a blanket solution to banking App issues.
1 Like
@tcecyk: thank you for the explanation, didn’t mean to write BS. So far I got every banking app running with Magisk and some modules. I really didn’t know some apps actually NEED Google Play Services that can’t be faked.
Only the first time. You can ask for a Digipass.
Idem with Trade Republic application (de.traderepublic.app); it gets killed when needing face recognition:
03-03 18:45:38.610 4216 5219 W DynamiteModule: Local module descriptor class for com.google.android.gms.vision.face not found.
03-03 18:45:38.610 4216 5219 I DynamiteModule: Considering local module com.google.android.gms.vision.face:0 and remote module com.google.android.gms.vision.face:0
03-03 18:45:38.617 879 5282 E mm-camera: <IFACE ><ERROR> 2441: iface_axi_handle_sof_event: Event SOF session 2 VFE1, src 0 with frame_id 75 ts: 328901019872000
03-03 18:45:37.467 18 18 E : [18:45:38.638103] [000005BE522FF876] [VosMC] wlan: [E :SME] Scan Request callback
03-03 18:45:37.467 18 18 E : [18:45:38.638125] [000005BE522FFA0E] [VosMC] wlan: [E :SME] Send scan result to PE
03-03 18:45:37.467 18 18 E : [18:45:38.638133] [000005BE522FFAB4] [VosMC] wlan: [E :SME] sme_RrmSendScanResult: 494: Allocated memory for SSIDList
03-03 18:45:38.641 4216 5301 W DynamiteModule: Local module descriptor class for com.google.mlkit.dynamite.face not found.
03-03 18:45:37.468 18 18 E : [18:45:38.638236] [000005BE52300268] [VosMC] wlan: [E :SME] sme_RrmSendScanResult: 520: Free memory for SSIDList
03-03 18:45:37.468 18 18 E : [18:45:38.638324] [000005BE52300907] [VosMC] wlan: [E :SME] Beacon report xmit Ind to PE
03-03 18:45:37.468 18 18 E : [18:45:38.638333] [000005BE523009AC] [VosMC] wlan: [E :SME] sme_RrmSendBeaconReportXmitInd: 213: Allocated memory for pBeaconRep
03-03 18:45:38.642 4216 5301 W DynamiteModule: IDynamite loader version = 2, no high precision latency measurement.
03-03 18:45:37.468 18 18 E : [18:45:38.638368] [000005BE52300C50] [VosMC] wlan: [E :SME] sme_RrmScanRequestCallback: 693: Free memory for ChannelList
03-03 18:45:38.644 4216 5301 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.face
03-03 18:45:38.644 4216 5301 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.face
Still no solution for that?
post your logcat with the appid in the title to the microg issues.
there is now partial mlkit support since late dec 2023. Implementing facerecognition seems a big feature, but just adding the dummy stub classes could keep traderepublic from crashing and maybe allow for a list of alternative means. Even if you cant do java/kotlin, creating stub classes is not hard, packaging it takes probably more time.