microg / microg/GmsCore

[com.triodos.bankinguk] Activating Mobile Secure Key fails

Open
#1,881 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Affected app
Name: Triodos Bank UK
Package id: com.triodos.bankinguk.325

Describe the bug
The bank offers to the ability to activate Mobile Secure Key which replaces a physical DigiPass for approving payments etc. on the app. To activate the Mobile Secure Key, the user needs to upload photos of an identity document (e.g. driving license) and a video of the user's face. I was able to upload the photos of the identity document but at the page for uploading the video, the following error message appears "Please install Google Play Services to continue". I have confirmed with the bank that their app does not support microG, receiving the following reply "The Mobile Secure Key is not compatible with MicroG libraries; Google Play services are a pre-requisite for using the Mobile Secure Key."

To Reproduce
Steps to reproduce the behavior:

  1. Download Triodos UK banking app
  2. Open the app and log in
  3. Click on Activate Mobile Secure Key under Feed
  4. Follow the instructions
  5. At the page where one has to take a video of one's face, the screen shows 'Please install Google Play Services to continue'.

Expected behavior
I am able to upload a video of myself and activate the Mobile Secure Key.

Screenshots
I took a log of the error that is split into two because of size limitations
part I
part II

System
Android Version: 10
Custom ROM: /e/OS1.5-20221031230909

microG
microG Core version: 0.2.24.223616-96 (f87cb98)-noen
microG Self-Check results: All ticked

Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Mobile Secure Key activation flow on Android 10 with /e/OS 1.5 and the reported microG version, then inspect the two linked log excerpts. Determine whether the Google Play Services requirement can be addressed in GmsCore; done would mean the video-upload step proceeds in this setup, or the limitation is documented with supporting evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
authentication, mobile
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.