Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Bugs found while taking v0.14.2 screenshots on an emulator (incl. data lost after first restart)

Abierto
  • ¿Algo no está bien?
#321 13 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@TimeToBuildBob ya está trabajando en esto.

Desde el 8/10/2026.

  • #325 de @TimeToBuildBob — fusionado
  • #326 de @TimeToBuildBob — fusionado
  • #331 de @TimeToBuildBob — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, kotlin
Área
backend, mobile

Línea de trabajo

This is a bundle of eight items; some already have PRs (#325 open, #326 merged) and item 1 is assigned, so check the thread first and pick a self-contained sub-item (5 dark mode, 6 back-swipe, or 4 /week/<date> snapping). For item 1, reproduce with fresh install → onboarding → POST bucket/events → force-stop → reopen and inspect /api/0/buckets/, focusing on where the DB is first opened/committed relative to first launch and WAL checkpointing. For item 2, start at the blocking thread start inside MainActivity.onResume and move it off the main thread. Done per item means its stated checkbox condition passes on a fresh emulator run.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Found while scripting marketing screenshots of v0.14.2 (release APK, universal) on an Android 16 emulator (AVD on CT 102, fresh install each run, demo data imported through the app's REST API at localhost:5600 with the API key from the app's config.toml).

@TimeToBuildBob this one is yours (assigned by Erik). Item 1 first; it may affect real users.

  • 1. Data written right after a fresh install is lost on the next app restart. Events and settings imported via the API vanished after the first app restart in the first 1–2 attempts of all 3 fresh runs; once the device had settled, imports survived restarts. Log buffer had rotated, so no root cause yet. Suspects: DB opened/committed before WAL checkpoint and the process killed, or the DB being recreated on first real start. Repro: fresh install → finish onboarding → POST a bucket + events → force-stop app → reopen → check /api/0/buckets/. Done when imported data survives a force-stop immediately after first launch.
  • 2. ANR on a fresh boot: "ActivityWatch isn't responding", main thread stuck in MainActivity.onResume while starting a thread. Move the blocking work off the main thread.
  • 3. Desktop-only tabs on Android: the bundled web UI shows the Window/Browser/Editor tabs, which only say "missing data from a required watcher" on a phone. Default Android to the Android views.
  • 4. Week view starts on the given date, not on Monday (/week/<date>), probably the same root cause as ActivityWatch/aw-webui#1058 item 1 (period not snapped to its start).
  • 5. Native sync settings screen ignores dark mode.
  • 6. With gesture navigation, back-swipe finishes MainActivity instead of opening the drawer or going back in the WebView.
  • 7. Fresh install shows "The saved aw-notify setting has an unsupported format" in Settings: already fixed upstream in ActivityWatch/aw-webui#1043, needs the web UI bump.
  • 8. Multi-device (@all, or several hosts) returns 0 s in the v0.14.2 web UI even with synced desktop buckets present; check after the web UI bump.

Screenshot script (re-runnable, ~8 min): CT 102 /root/aw-screenshots/android_screenshots.py --wipe.

Lenguaje dominante
Kotlin
Estrellas
277
Forks
61
Merge medio
2 d 4 h
PR fusionados (30 d)
52

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ActivityWatch/aw-android

Todos los issues de ActivityWatch/aw-android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.