Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

android: beta launch checks (upgrade from 1.0.10, free path, release build, local, Auto/Cast, data safety)

Aperta
  • Qualcosa non va?
#1,044 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
mobile, release, testing-qa

Direzione di ricerca

This is a pre-release QA checklist, not a code change: each item needs a physical Android device, Play builds and a server account. Start by reading the linked issues (#940, #380, #1031, #1037, #1040) and the existing 1.0.10-vs-main comparison, then the device steps the issue says belong in docs/testing/device-checks.md. Done means every checkbox is run and its result recorded there, with any regressions filed as separate bugs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement impact:U3 next-release owner P1 reach:R3 size:M

These are checks to do before widening the next Android beta beyond internal testing. The 1.0.10-vs-main release comparison only covered a fresh install of a debug build against Emby, so these weren't exercised.

  • Upgrade from 1.0.10. Install the Play 1.0.10 build, add playlists, favourites, play counts, a server and a local folder. Then install a release-signed new build over it and check that everything survives (data, settings, server credentials, the legacy restore from #940). Production and about 10k open testers will upgrade, not install fresh.
  • Free/trial path. Debug builds are always Pro. On a release build from the internal track, as a non-Pro account, check the trial, paywall copy (#380), limits and the Settings Pro card.
  • Release build smoke test. Every capture used a debug build. Run the release build on a real device: browse, play, sign in to a server, download, Cast.
  • Local music first run. Folder setup and scan on a device with local files (#1037, #1040).
  • Android Auto, Chromecast, home-screen widget, media notification and Quick Settings tile.
  • Play data-safety form matches the telemetry defaults (#1031, #1040). (owner)
  • Sentry. No new crash clusters from the internal track before widening.

Device steps belong in docs/testing/device-checks.md for the batch run.

Impact U3 (an upgrade or paywall regression would hit every beta user) · Reach R3 (every upgrading user; not yet tested) · Implemented: no · Design fit: fits · Complexity: M

Lingua principale
Kotlin
Stelle
229
Fork
28
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di timusus/Shuttle2

Tutte le issue di timusus/Shuttle2

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.