[de.dm.meindm.android] Every login attempt fails because of reCAPTCHA error
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: Mein dm
Package id: de.dm.meindm.android
Describe the bug
When trying to log into the app, it fails with a generic error message in a dialog. When checking logs, it reports the following:
08-12 23:06:16.121 10455 10455 E c : Error while performing ReCaptcha action: com.google.android.recaptcha.RecaptchaException: Site key invalid (additionalDatadogAttributes = [team=ciam, dm-costcenter=1023313353, subsystem=Recaptcha, reason=RECAPTCHA_INVALID_SITEKEY])
08-12 23:06:16.125 10455 12794 E a : Error during login: INVALID_SITEKEY (additionalDatadogAttributes = [team=ciam, dm-costcenter=1023313353, subsystem=Authentication, reason=RECAPTCHA_INVALID_SITEKEY])
To Reproduce
Steps to reproduce the behavior:
- Go to "Jetzt anmelden" (login now)
- Enter any email and password
- Look at log
Expected behavior
ReCaptcha works
Screenshots
N/A
System
Android Version: 15
Custom ROM: LineageOS 22.2
microG
microG Core version: 0.3.9.250932
microG Self-Check results: All ticked, except "Permission to interact with work profile"
Additional context
This has been a problem ever since the app switched from a browser-based login to a native login view.
It seems like they are just using reCAPTCHA Enterprise SDK.
Both "Test ReCAPTCHA" and "Test ReCAPTCHA Enterpise" in microG's settings pass.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository file, test, or entry point. Start by reproducing the Mein dm native login flow on Android and tracing the reported reCAPTCHA Enterprise INVALID_SITEKEY error; compare it with the existing reCAPTCHA test results in microG settings. Done means the login attempt completes without the site-key error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100