mirror of
https://github.com/readest/readest.git
synced 2026-07-09 16:00:16 +00:00
21ebf10489
Some checks are pending
CodeQL Advanced / Analyze (actions) (push) Waiting to run
CodeQL Advanced / Analyze (javascript-typescript) (push) Waiting to run
CodeQL Advanced / Analyze (rust) (push) Waiting to run
Publish Docker image / build (linux/amd64, ubuntu-latest) (push) Waiting to run
Publish Docker image / build (linux/arm64, ubuntu-24.04-arm) (push) Waiting to run
Publish Docker image / merge (push) Blocked by required conditions
Scorecard supply-chain security / Scorecard analysis (push) Waiting to run
Deploy to vercel on merge / build_and_deploy (push) Waiting to run
PR checks / build_tauri_app (push) Waiting to run
PR checks / rust_lint (push) Waiting to run
PR checks / build_web_app (push) Waiting to run
PR checks / test_web_app (1) (push) Waiting to run
PR checks / test_web_app (2) (push) Waiting to run
PR checks / test_extensions (push) Waiting to run
Google Play rejected the latest release in Android Auto review because the Auto TTS integration still has a bug. Remove the com.google.android.gms.car.application meta-data, which is the sole signal Play uses to detect Android Auto support, so the release can be resubmitted through normal review. The MediaBrowserService intent-filter and MediaButtonReceiver stay as they power the phone lock-screen and background TTS media session and do not trigger Auto detection. The automotive_app_desc.xml resource is kept so re-enabling the feature after the bug fix is a one-line revert. The Android Auto declarations test now asserts the car meta-data is withheld until the bug is fixed, while still checking the descriptor and MediaBrowserService remain in place. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| readest-app | ||
| readest-calibre-plugin | ||
| readest.koplugin | ||