de.number26.android N26: cannot pair smartphone
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: N26
Package id: de.number26.android
Describe the bug
I'm not entirely sure if it's a MicroG problem, but maybe someone has other inputs to try:
When pairing the N26 app and the smartphone, an E-Mail message is sent to verify the address. This seems to work and the N26 app displays "E-Mail successfully verified". However, at the end of the linking process, as soon as the confirmation code is entered, the N26 app displays an error message indicating that the E-Mail address needs to be verified.
To Reproduce
Steps to reproduce the behavior:
- Got to N26 app, log in with SMS code
- Start smartphone pairing process
- Verify E-Mail address and enter personal code
- See error
Expected behavior
After step 3, a success message and a paired smartphone app.
Screenshots
If applicable, add screenshots to help explain your problem.
System
Android Version: 13
Custom ROM: LineageOS for MicroG 20240101
microG
microG Core version: 0.3.0.233515 (didn't work with 0.2.27.223616 either)
microG Self-Check results: All ticked
Additional context
Magisk and Shamiko also installed, SafetyNet passes.
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 report names no source file, test, or entry point. Start by reproducing the N26 smartphone-pairing flow on Android 13 with the listed microG versions, then investigate where email verification state is handled after the confirmation code. Done means identifying a reproducible microG cause or documenting that the failure is outside this project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100