PhilippC / PhilippC/keepass2android

[BUG] Received unexpected response

Open
#2,985 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

Checks
  • I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:

On a Realme RMP2013 (Android 10 to12) and on two different devices "Tabwee W90" (Andr. 15) with "Nova Launcher" I have always the same error. See sreenshot. No difference in landscape or portrait mode.

Image

Describe what you expected to happen:

I have multiple phones with Android OS (A8-A15), all with "Nova L." and the Keepass has no problems with the phones! (And even my Chromebook now is working with Keepass2Android.)

What version of Keepass2Android are you using?

1.12-r5

Which version of Android are you on?

15 (W90_EEA_L30_v1.0_A15_01_20250222V03...)

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

No source file, test, or entry point is named. Start by reviewing the attached screenshot and reproducing the unexpected response on Android 15 with Keepass2Android 1.12-r5, then compare behavior across the reported devices and Nova Launcher. Done means identifying the cause and confirming the response is corrected without regressing the working devices.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.