Automattic / Automattic/pocket-casts-android
Android Auto through BMW Connected >Skip Forward/Back function does not work
- Dominant language
- Kotlin
- Stars
- 2.8k
- Forks
- 308
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 143
Description
> When connected via this method the Skip Forward/Back function does not work. I raised an issue with the developer and they say it is due to how you guys surface that function. It is slightly over my head but the request seems to be
On MediaController, AAI maps the Back/Next screen commands or buttons to the MediaController's Back/Next commands, but PocketCasts uses the Skip command instead. The ask is for PocketCasts to replicate the Skip forward/back function to the MediaController Back/Next commands. There was also a comment that Spotify sets a flag when playing an audiobook but that may not be needed in the case of a PodCast application as everything should be treated as an audiobook (or am I missing something on that).
Full issue details are here along with a discussion with the developers: https://github.com/hufman/AndroidAutoIdrive/issues/350
Contributor guide
Research direction
Start with the AndroidAutoIdrive issue linked in the report and trace how Pocket Casts exposes MediaController commands for Android Auto. Confirm the expected Back/Next mapping from that discussion, then verify that Skip Forward and Skip Back work through BMW Connected; no project files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100