PhilippC / PhilippC/keepass2android
[BUG] k2a on chromebook does not work
Nobody has claimed this yet.
- 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:
New problem on Google_Vilboz.13434.576.0 Zork and Android 13 in Chomebook-Playstore. App starts, seems to be running for a few seconds and the app ends without an error message. After deleting cache and/or data you can attach to google drive, but after a few seconds ends the app also without a message.
[edit]
Seems to be a permission problem. Camera and contacts can be enabled but i could not give access to the file system.
[edit2]
App de-inst and re-inst after a needed chromebook reboot for v120. No change, app ended without an error message. Version 1.10-PRE did not ask for file access on 2 devices.
Can somebody check the needed permissions on your devices?
Google Chrome: Version 120.0.6099.235 (Official Build) (64-bit)
Platform: 15662.76.0 (Official Build) stable-channel zork
Chrome ARC Android SDK Version: 33
ChromeOS Firmware Version: Google_Vilboz.13434.576.0
ARC Enabled: true
ARC: 11277367
Channel: stable-channel
Enterprise Enrolled: false
Developer Mode: false
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
1.10-PRE
Which version of Android are you on?
13
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
Start by reproducing the crash on Google Vilboz Chromebook with ChromeOS stable, Android 13, and Keepass2Android 1.10-PRE, focusing on the reported file-system permission behavior. Check available device logs because the report gives no source file or test entry point. Done means the app no longer exits silently and required file access works on the affected Chromebook configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100