Do you mean Aurora Store does NOT work?
2 Likes
If you are in the EU (I’m not), they have given you the DMA. Google is a gatekeeper, and some API’s are anti competitive, like this. Join St Max doing God’s work.
Also think of Article 11 of the ECHR which protects “freedom of association”
An unconsidered aspect of that is that in the tech era you are being compelled to associate with both foreign corporations, and the govt’s whose security laws they must obey. The ECHR probably only bears on the State compelling you, not private actors. It might however be used e.g. to stop a govt dept from exclusively distributing it’s apps on Play store and IoS only.
I am currently using this argument to stop my (state funded) university forcing me to agree to a contract with the Turnitin anti-cheating service as a condition of submitting assignments.
2 Likes
Yes, the app detects it hasn’t been installed by the Google Play Store, and prevents me from logging in.
It still works. You can set ‘Installation method’ as ‘AM installer’ in AuroraStore and use App Manager from F-Droid. In App Manager->Settings->Installer>Installer App->com.android.vending
2 Likes
Is the fix supposed to be just what you’ve described there, or is there further, app-specific tweakage needed as well? I tried it with the app “Hanseatic Bank Secure” (as mentioned in the Wiki above by me), with “MicroG Companion/com.android.vending” acting as installer app with App Manager, however it still complains about the “App download being untrustworthy”, just as it did before via Aurora Store’s session install method.
1 Like
No additional app tweaking is required. Setting com.android.vending in AppManager is the same as choosing Native Installer(now marked as deprecated) in Aurora Store.
It looks like your banking app uses additional methods of “trustworthiness” checking :).
1 Like
You speak of “com.android.vending”, however on my end it is (being the sole “com.android.vending” entry in App Manager’s list) labelled with “MicroG Companion” on top. Is having MicroG installed already a given pre-requisite anyway in your step-by-step instructions, or could that be another source for issues?
“com.android.vending” is a string that “Google Play Store” sets during install process and some banking apps are checking this string to confirm that is installed from Play Store. App Manager shows MicroG because MicroG has registered this string in AAS.
Regarding banking app and its requirements MicroG itself is another issue.
4 Likes
Alright, thanks for elaborating.
Yeah, its the same like the discussion of the ingdiba app above. The app is checking the installation source.
That’s unfortunate. Maybe the installation method via the App Manager mentioned above can help with this.
It is really good to have all this information here, so you can check a benk before switching to it
You are correct, this fix did work for me!
So I can confirm polish ING app works on SFOS after jumping through some hoops.
3 Likes
We should lobby to EU to mandate some banking app standards. Right now, banking apps effectively enforce a mobile duopoly: App Store and Google Play. They will never bother with anything else, so other platforms will remain niche.
One realistic solution could be to force them to make most functionality available to a web browser, plus perhaps some browser containerization for the sake of security.
8 Likes
Currently on Sony Xperia 10III and SFOS Sauna 4.6.0.15 (and MicroG 0.2.27.223616), I am unable to use Danske Bank Mobiilipankki. It informs me that it can only be used on one device at a time, and the device binding must be renewed. Then it fails at logging in: after I’ve entered my account and password, it never asks for the 2nd authentication factor, but immediately returns back to the single device popup. Suggestions?
And just after writing this, I was able to solve the problem: uninstall the whole application and then reinstall. At that point I was presented with the choice of which kind of 2nd factor authentication I want to use, and using the code generator dongle it went through.
6 Likes
Is there an intentional reason why you are using an old MicroG version from January 2023? The most recent one is 0.3.3.240913 (albeit with a small regression, that may or may not affect you, which will be fixed soon in a new release): Releases · microg/GmsCore · GitHub (the two relevant packages for our purposes are always com.android.vending-(numbers).apk and com.google.android.gms-(numbers).apk).
That was what I installed to make Mobilepay work, and no updates from this version have been offered by F-Droid. Should it have done this automatically?
I’m not sure if F-Droid “offers” the updates unless the new version is marked as recommended, but you can always check the versions every now and then under Settings -> Manage Installed Apps -> MicroG/any other app -> Versions
1 Like
Normally yes, but I guess sometimes it doesn’t work as intended or only with a big delay. MicroG gets updates so infrequently, that updating it manually through GitHub shouldn’t be that much of a hassle, that way the updates get installed 100 % reliably and in time.