Refresh Now workaround on Android Automotive doesn’t work

  • Unknown's avatar
    glacionc01f02daf6 · Member ·

    Regarding the workaround from: https://forums.pocketcasts.com/forums/topic/sync-issue-playback-starts-from-correct-place-but-immediately-jumps-back/

    Using Refresh Now manually doesn’t seem to work if the episode is already in Now Playing state (even if the playback is paused) because by the time I can get to the Refresh Now button, it has already saved the older (incorrect) timestamp. Just wanted to make sure the devs were aware of this.

  • Unknown's avatar
    glacionc01f02daf6 · Member ·

    I’m having a strange issue when playing an episode, the two devices are my Android phone and my Android Automotive car.

    On my android phone, I start playing an episode:

    I 17/3 16:14:26.052 Play 195.796 System Player. Boston Does L.A., Honeymoon Harden, a Denver Hiccup, and a Kawhi Deep Dive With Zach Lowe Downloaded: false, Downloading: false, Audio: true, File: https://pdst.fm/e/traffic.megaphone.fm/GLT1312161723.mp3, EpisodeUuid: 66dbb0a8-4cc2-4ee3-bcfb-c9a0afec3d4f, PodcastUuid: d6d843f0-45f5-0133-c150-0d11918ab357
    I 17/3 16:14:26.059 LocalPlayer onSeekComplete 195.796
    I 17/3 16:14:26.085 Saved time in database 195.796

    Eventually I stop playing, and it saves the time to database:

    I 17/3 16:58:38.884 Saved time in database 4060.126

    But when I start playback from my car in the AAOS app, the playback bar seems to momentarily show progress up to 4060 timestamp for a brief second, and then jumps back to a much earlier timestamp and plays from there.

  • staff-joey8 · Staff ·

    Hi there, @glacionc01f02daf6

    Our team is aware of this and we have it documented here: https://support.pocketcasts.com/knowledge-base/known-issues/

    As a workaround, you’d need to use the ‘Refresh Now’ button on AAOS to ensure it syncs the latest data from our servers.

  • staff-eleanor · Staff ·

    Hi there! Thanks for the update! I’ve shared it with the team. We’ve merged your forum threads so we can track the issue.

    If you’re willing, the most useful next step would be to grab logs right after this happens so the team can see the exact sequence of events. You can get them via the mobile app (Profile > Help & feedback > Contact Support > Get Support), then send them through support with a short description of your car model, Android Automotive version, and the steps you took.

    Would you be able to share what car model and Android Automotive version you’re using so we can include that context for the developers?

Reply to Refresh Now workaround on Android Automotive doesn’t work