Banking app works on older device with microG but not on newer device

[summersab]

Describe the bug The Capital One banking app fails to load on my OnePlus 7 Pro running LOS + microG. It worked a few months ago on the same device. Strangely, it works just fine on my old Nexus 5X running LOS + microG. What changed?

I know there are lists of apps that are known not to work under microG, but the fact that it used to work indicates something must have changed. Perhaps there is a fix?

System Working device Device: Nexus 5X (bullhead) Android Version: 11 Custom ROM: LineageOS 18.1-20220422-UNOFFICIAL-bullhead microG Version: 0.2.17.204714 Download Link: https://androidfilehost.com/?fid=14655340768118461182

Broken device Device: OnePlus 7 Pro (guacamole) Android Version: 14 Custom ROM: LineageOS 21-20240507-microg-guacamole microG Version: 0.3.2.240913 Download Link: https://download.lineage.microg.org/guacamole/

Additional context It was a long time ago since I set up my Nexus 5X. I don't remember if the ROM I installed came with microG installed or if I flashed it separately, but I think it was included in the build.

[ale5000-git]

You are years behind, before reporting you should at least update microG to v0.3.2.240913 :-)

[summersab]

Strange - I upgraded via F-Droid, but it kept me on an older version. I just installed the latest. My banking app still won't launch. Things I've tried:

• Clearing all app data, granting all permissions manually (including disabling battery optimization), enabling GPS, camera, and microphone access, and opening the app
• Disabling SafetyNet
• Disabling device registration
• Enabling animations (that sometimes makes things wonky)

Are there other tips or tricks I could try?

Also, Slack stopped working about a week (maybe two) ago. I don't know if this is a microG issue or not, but I thought I would mention it.

[ale5000-git]

Be sure to:

• First update microG Services to v0.3.2.240913;
• Then update microG Companion to v0.3.2.240913;
• Go into microG self-check to verify everything is checked;
• At the end uninstall and reinstall the apps that have problems.

Some apps may need device registration and cloud messaging to be enabled.

[summersab]

Summary I discovered that the following versions work and allow Capital One to launch without issue (the latest versions do NOT work):

• microG Services: 0.2.29.233013
• microG Companion: 0.3.0.37524

Details Interesting discovery. An OTA update broke my phone, so I had the opportunity to wipe my device and start fresh. I used the following image from the LineageOS for microG project: lineage-21.0-20240507-microG-guacamole.zip

By default, it comes with the following (both marked as "Suggested" in F-Droid):

• microG Services: 0.2.27.223616
• microG Companion: 0.2.1

The Capital One app fails to load and just shows the splash screen. Instead of upgrading to the most recent microG versions, I did this:

1. Incrementally upgrade both microG apps using F-Droid
2. Wipe the Capital One storage and manually grant permissions
3. Disable device registration and SafetyNet
4. Try launching Capital One
5. Upon failure:
   • Start at step 2 and enable device registration at step 3
   • If it failed again, start at step 2 and enable SafetyNet at step 3
   • If it failed again, start at step 1 and upgrade to the next version(s) of microG

Basically, I tried all combinations of registration and SafetyNet before moving to the next version(s) of microG.

Finally, I installed these versions, and the Capital One app opens right up. Enabling or disabling device registration and SafetyNet makes no difference:

• microG Services: 0.2.29.233013
• microG Companion: 0.3.0.37524

I have not tried upgrading microG further because I don't want to break anything after finding versions that work. I know from my previous install that the latest versions of microG do NOT work with the Capital One app. Something changed between versions that cause Capital One (and probably other apps) to fail.

Let me know what I can do to help investigate the issue. I'm a web developer with minimal experience doing Android development, but I know how to build apps, use adb, and am familiar with debugging with Android Studio. If absolutely necessary, I can upgrade the microG apps to see which versions eventually break, but I would prefer to avoid the hassle of backing up and restoring my phone in case the upgrades fail (it's time consuming and a pain in the backside).

[ale5000-git]

Starting from v0.3.0 they are released together and it is opportune to have matching versions of microG Services and microG Companion. microG Companion use features from microG Services, so it will be partially not functional with an old microG Services.

I suggest to wait version v0.3.3, update both (first microG Services and then microG Companion, in this order) and then take a logcat.