It isn’t SafetyNet. I’ve tried again on another device running Lineage for microG on which SafetyNet passes. I get exactly the same result.
It could be that they detect a custom ROM is running, and the stuff about Google Play Services is just the message they use. Or they are using a GPS API which microG doesn’t implement.
I’m not going to get into debugging this just yet. I’ll wait for the response from the bank. In the meantime I can login to internet banking using my phone’s browser (which I prefer to do anyway)
When i complain to the “Credit Agricole” that i have to root my device to be abble to run their app “Ma Banque” and ask them to correct that bug, they aswer that their app cannot run on a rooted device, (LoL).
They advise me a app (witch give interresting informations) to diag the different system settings : “RootBeer Sample” available in “AuroraStore”
@piero while this applies to CA, it can be detrimental pointing to Safetynet whenever a banking App has difficulties. A switch from dev to stable build could involve a userdata reset - unpleasant. Without tangible result in case of the tridos uk bank app. The issue really needs a bit of debug info to continue
The Mobile Secure Key is not compatible with MicroG libraries; Google Play services are a pre-requisite for using the Mobile Secure Key.
It looks like it is still possible to use the app if you have a DigiPass. It’s not clear whether you wouldneed to use the DigiPass each time you want to use the app, or whether it’s only the first time
I got the same response from them. I do have (and use) the DigiPass but from what I understand they’re planning to phase it out, hence the need for Mobile Secure Key (or just telephone banking…), though they did say that they won’t “leave you without a way to access your accounts.” so perhaps they won’t phase out the DigiPass just yet.
Hmm I guess it’s ultimately up to me to decide whether I want to upgrade to R (which is to Android 11?) which may possibly solve the issue, but could be a lot of trouble?
I’ll try and see if I can get a log from my phone to submit the issue…
Hmm seems like a tough choice, one does wish Google would let up on its hegemony…
Hi sorry could you include the link to where I can report this issue? I’ve got the logcat for the error (though I don’t know if microg can do anything about it since it’s the app that requires Google Play Services and isn’t compatible with microg?), but not quite sure where I’m supposed to post it to.
Also, could you advise if I can remove my email addresses from the logcat file (I don’t quite know what’s going on in that file but I can see from looking through it that the email addresses linked to accounts on my phone appears in there)?
It’s due to not implemented parts of the GMS Vision API (it only does barcodes, not QR or Face) - see github
3229 3255 D ChimeraServiceProvider: query: content://com.google.android.gms.chimera/api_force_staging/com.google.android.gms.vision.ocr?requestStartTime=414613693
28090 31031 I iodos.bankingu: The ClassLoaderContext is a special shared library.
28090 31031 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.ocr
28090 31031 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.ocr
28090 31034 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.face
28090 31034 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.face
(btw: theres a segfault on the browser in there right at the start, that’s funny. Probably a reason to update /e/ itself)
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.
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
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.
@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.
