PhilippC / PhilippC/keepass2android

[QUESTION] Privacy file authorization cannot be disabled and blocks password database import

Open
#3,208 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

In the new MIUI system (HyperOS), privacy file authorization causes an issue when reading the password database. This privacy protection cannot be turned off. Even for files that are not in Android's critical folders (e.g., files under the Android directory), the system still enforces read-only restrictions.

When trying to access the password database, it shows a message that the file is read-only and suggests copying it to another folder.("The file you selected is read-only for Keepass2Android due to restrictions on Android 4.4+. To edit it, you must copy the file to another location. Tap OK to select a location where the file should be copied.")
However, attempting to create a copy fails with an error: "An error occured:
UnauthorizedAccess_IODenied_Path, /storage/emulated/0/Keepass//.kdbx". As a result, the password database cannot be imported properly.

Version:1.14-r0

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 password-database import on MIUI HyperOS with Keepass2Android 1.14-r0, using a file under the Android directory. Trace the copy step that produces UnauthorizedAccess_IODenied_Path and compare its behavior with Android file-access restrictions; done means the database can be imported without the read-only copy failure.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.