arn-c0de/Geograbber

🐛 Issue: Crash when activating external .db if confirmed too quickly

Open

#24 opened on Nov 3, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Java (3 forks)auto 404
area: databasebughelp wantedjavamediumneeds reviewperformance

Repository metrics

Stars
 (30 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

When importing an external .db file and clicking “Yes, Activate” immediately in the Set External Database as Active window, the app throws an error and the import crashes.

Reproduction

  1. Open Import External Database.
  2. Select a .db file.
  3. As soon as the Set External Database as Active dialog appears, click “Yes, Activate” quickly, before the Android biometric key prompts appear.
  4. Crash occurs.

Cause (suspected)

Activation is triggered before biometric key initialization finishes.

Proposed Fix

Add short delay or await biometric key readiness before allowing activation.

Contributor guide

Research direction
Inspect the biometric key initialization flow and ensure the activation waits for readiness by adding a check or delay.
Tech stack
java
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitAndroid SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75