Skip to content

Instantly share code, notes, and snippets.

@jubishop
Last active February 5, 2026 19:39
Show Gist options
  • Select an option

  • Save jubishop/ccd74f2d503d20d2bae81183ede18366 to your computer and use it in GitHub Desktop.

Select an option

Save jubishop/ccd74f2d503d20d2bae81183ede18366 to your computer and use it in GitHub Desktop.
review.md

⏺ Based on my analysis, none of the changes since commit 1183550f4fbc would have caused this issue. Here's why:

Changes to playback code:

  1. All the PlayManager/PodAVPlayer changes are our debugging additions - These are purely additive (logging, error handling, isCurrentItem check). They don't
    modify any core playback behavior.
  2. The only pre-debugging change was d08b406f which makes pause() async to save position immediately - this doesn't affect playback mechanics.

Other changes:

  • HTMLText parsing improvements
  • Chapter navigation (new feature)
  • Share functionality
  • Episode timestamp formatting
  • ErrorKit helpers

The -11800 error (AVErrorUnknown / "Cannot Decode") is an AVFoundation error that happens at the media layer, not in app code. Common causes:

  • Corrupted or incomplete cache file
  • Network hiccups during streaming
  • iOS resource pressure
  • Media Services framework instability
  • Audio route/session interruptions not being handled

The fact that this seems to be happening consistently for one user around the same time of day (~7:40-7:45 AM) suggests it might be environmental - perhaps related to their device's routine (backup, sync, background activity) or network conditions at that time.

This appears to be an environmental issue rather than a regression from recent code changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment