Make sure the app is uptodate
no additional information unfortunately:
10-30 15:13:25.698 21768 21840 I ¯\_(ツ)_/¯ : OKHTTP [400] https://android.clients.google.com/fdfe/purchase?ot=1&doc=com.barclays.android.barclaysmobilebanking&vc=0
10-30 15:13:25.798 21768 21840 I ¯\_(ツ)_/¯ : OKHTTP [200] https://android.clients.google.com/fdfe/delivery?ot=1&doc=com.barclays.android.barclaysmobilebanking&vc=0
10-30 15:13:25.801 21768 21768 E ¯\_(ツ)_/¯ : Failed to purchase Barclays : App not supported
(have a hard time figuring out the acronym “fdfe” for the /fdfe/purchase and /fdfe/delivery endpoint. DFE in android can mean disable-forced-encryption, but that makes no sense)
There was an old barclay related bug in microg (6 years old). Since safetynet passes (can you do a self check in System->microg->safetynet?) according to the thread it’s no longer needed: DroidGuard Helper For Barclays Banking App · Issue #206 · microg/GmsCore · GitHub
i have found the fdfe api path in other issues, but not the “purchase” request Barclays it is failing on.
- Google Play Store Error - No account configured on this device. · Issue #110 · microg/GmsCore · GitHub
- SafetyNetHelperSAMPLE: ApiException[14] · Issue #780 · microg/GmsCore · GitHub
Someone intimate with API endpoints can maybe shed light on this? must be something the playstore client can call?
So when run “Test SafetyNet attestation” under the “Google SafetyNet” settings, I get the error “Warning: CTS profile does not match”.
for “cts profile” mismatch you can find many posts in the forum and gitlab backlog. It doesn’t have to be a bug when the attestation fails for something it checks for.
I guess it trips up on it being rooted, but I’m sure this can be fixed by some magisk module too - the likes of magiskhide or
https://github.com/kdrag0n/safetynet-fix
This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
Thanks,
So I installed that module as well as the “MagiskHidePropsConf” one and edited the device fingerprint, and now the SafetyNet checks pass. However, still no luck downloading the Barclays app, still the same issue “App not supported” 
on both applounge and aurora?
the log string “Failed to purchase” I can’t find via cs.android.com or in applounges source. Can you give more context from the logcat, what the processid 21768 and 21840 belonged to, what is emitting that line?
I gave this a go on a v1.4 fp3 on R/dev and I could install the app that was named “Barclays” with appid com.barclays.android.barclaysmobilebanking - login screen showed up after install. I went through AppLounges search interface.
I can’t attempt an install via the AppLounge because it doesn’t appear when I search for it. It doesn’t appear when I search on Aurora either, but I can get to the Aurora page by launching the Play store link to the app on the Barclays website.
21768 is com.aurora.store
21840 I don’t know. Each time I try to install the app then view the logcat, that ID changes. If I immediately run “adb shell ps -A” after attempting to install and checking the logcat for the ID, the ID in question is not listed.
I guess the App is filtered for you then - AppLounge is using the same google-play API Aurora introduced - Unsupported app! in App Lounge - #23 by luc_pcm (see conclusion at the end) … it might be a bug if it’s filtered for invalid reasons though.
You can grab the appid apk from somewhere and try a streamed install via adb. Just make sure to check and compare the apk signature on it if it’s widely used, that good enough.
For a Moto Harpia the appid is filtered - so some filtering is going on, it might be device or region based - Barclaycard Deutschland not available (#669) · Issues · Aurora OSS / AuroraStore · GitLab
OK so I found an APK and verified it using APK Pure’s apk signature verification tool.
However, when I try to install it via ADB I get the error:
`adb: failed to install banking.apk: Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY: Reconciliation failed...: Reconcile failed: Package com.barclays.android.barclaysmobilebanking requires unavailable shared library com.google.android.maps; failing!]`
This is the logcat:
10-31 15:26:10.498 5628 5671 W PackageParser: Unknown element under <manifest>: queries at /data/app/vmdl275196226.tmp/base.apk Binary XML file line #21
10-31 15:26:10.587 5628 5671 W PackageManager: Reconciliation failed...
10-31 15:26:10.587 5628 5671 W PackageManager: com.android.server.pm.PackageManagerService$ReconcileFailure: Reconcile failed: Package com.barclays.android.barclaysmobilebanking requires unavailable shared library com.google.android.maps; failing!
10-31 15:26:10.587 5628 5671 W PackageManager: at com.android.server.pm.PackageManagerService.reconcilePackagesLocked(PackageManagerService.java:16854)
10-31 15:26:10.587 5628 5671 W PackageManager: at com.android.server.pm.PackageManagerService.installPackagesLI(PackageManagerService.java:17215)
10-31 15:26:10.587 5628 5671 W PackageManager: at com.android.server.pm.PackageManagerService.installPackagesTracedLI(PackageManagerService.java:16504)
10-31 15:26:10.587 5628 5671 W PackageManager: at com.android.server.pm.PackageManagerService.lambda$processInstallRequestsAsync$14$PackageManagerService(PackageManagerService.java:14785)
10-31 15:26:10.587 5628 5671 W PackageManager: at com.android.server.pm.-$$Lambda$PackageManagerService$6_Yp7BSB4TgtrWSoFlODKgHIvZY.run(Unknown Source:6)
10-31 15:26:10.587 5628 5671 W PackageManager: at android.os.Handler.handleCallback(Handler.java:883)
10-31 15:26:10.587 5628 5671 W PackageManager: at android.os.Handler.dispatchMessage(Handler.java:100)
10-31 15:26:10.587 5628 5671 W PackageManager: at android.os.Looper.loop(Looper.java:214)
10-31 15:26:10.587 5628 5671 W PackageManager: at android.os.HandlerThread.run(HandlerThread.java:67)
10-31 15:26:10.587 5628 5671 W PackageManager: at com.android.server.ServiceThread.run(ServiceThread.java:44)
10-31 15:26:10.599 5628 5628 W Binder:5628_C: type=1400 audit(0.0:200): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:shell:s0 tclass=unix_stream_socket permissive=0
10-31 15:26:10.599 5628 5628 I chatty : uid=1000 system_server identical 1 line
10-31 15:26:10.599 5628 5628 W Binder:5628_C: type=1400 audit(0.0:202): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:shell:s0 tclass=unix_stream_socket permissive=0
10-31 15:26:10.599 13711 13711 W adbd : type=1400 audit(0.0:203): avc: denied { shutdown } for scontext=u:r:adbd:s0 tcontext=u:r:shell:s0 tclass=unix_stream_socket permissive=0
10-31 15:26:10.606 5512 5622 I netd : firewallSetUidRule(2, 10053, 1) <0.09ms>
10-31 15:26:10.608 5505 5701 E : Couldn't opendir /data/app/vmdl275196226.tmp: No such file or directory
10-31 15:26:10.608 5505 5701 E installd: Failed to delete /data/app/vmdl275196226.tmp: No such file or directory
10-31 15:26:10.608 5628 7087 D PackageInstallerSession: Ignoring abandon after commit relinquished control
10-31 15:26:10.622 5794 5794 W IntentFilterVerificationReceiver: Error when processing input Android package: com.barclays.android.barclaysmobilebanking
10-31 15:26:10.622 5628 5671 W PackageManager: IntentFilterVerificationInfo not found for verificationId:2 packageName:com.barclays.android.barclaysmobilebanking
dejavu - filed this a few days ago at
maybe a missing maps layer surrogate (mapbox is doing this) is the original reason the app got removed?
certainly looks like the same issue, only difference being I can’t even find the app in the app store when searching. I suppose will just have to wait for a fix?
as you’ve rooted your phone, you can provide system packages at any time… must be this one
magisk should be able to handle that zip
I tried loading it in magisk, but it was not accepted as it was not recognised as a module.
I tried to adb sideload it but got a different error. Not sure how I’m supposed to apply it exactly?
1 Like
uhm sorry, it’s this easy, either via adb or with twrp: Installation · microg/android_frameworks_mapsv1 Wiki · GitHub
The magisk’s modified /boot should have been overwrited by the /e/OS updater …
thanks, don’t do these things so often so forgive my noobness!
pushed files via adb, rooted, app now installed (had to use sourced APK though as I still couldn’t download via app store for some reason)
Thanks for help!
1 Like
you can mark the post that solved it for others for easier downscroll - though I understand why it’s filtered for you in AppLounge wasn’t resolved
update: since updating to eos 1.5, the app now appears in the store. I still had to push the map files for it to install
I linked this thread at FP3 v1.4 stable Q build is missing com.google.android.maps prebuilt apk (#6161) · Issues · e / Backlog · GitLab - I dont understand why not more s9 stable users seem affected