Cannot sync podcasts on Plex Mobile - says I need a newer server

Server Version#:4.34.4
Player Version#:7.6.0.6748 (aaa5077c)

On an episode page for a podcast if I tap the 3 dot menu and select Sync I get:

As you can see my Plex Media Server is not too old at all. What is “sync” supposed to do that is different from say “download”?

That is not the server version. That’s the Web player. Look further down on the left for “General” listed under the name of your server.

I think this is the bigger issue. That’s an old version of the app so it’s probably not talking to your server correctly and then giving the wrong reason for the problem.

Version 1.20.2.3402 Check for Updates Up to date

Hmmm… I just installed the Beta version of Plex hoping some of my problems have been fixed. That is the version number that the Plex Mobile app reports.

Uninstalled beta and installed from the Play Store and got 8.7.2.20952 (5f6d7f6b). With this version, there are no Podcasts to be found!

To add on - I got the beta versions from Android (mobile) beta release notes. Funny thing is that I couldn’t install it. I said simply “app not installed”. (Is it just me or are error messages getting worse). I had to uninstall the standard Plex app and install the beta again. IOW the beta would not install over the non-beta.

Did you get the beta from Android (mobile) beta release notes - #369 by sixones?

That’s the current public release, not beta. Did you exit the beta program? Android App Testing - Google Play

Either way. Even with the public release, you should see podcasts. Did you look under the “more” option at the bottom?

Yes, I got it from there. No, I exit the beta program. I wasn’t even sure if I had signed up for the beta program so I tried and I got:

** App not available for this account

Your account isn’t currently eligible for this app’s testing program.

If you’ve been invited to become a tester, make sure you’re signed in to the account that was invited to the testing program. If you’ve been invited to a Google Group as part of the program, make sure you’ve joined the Group.**

Still, I was able to download and install the beta (by removing the standard version first.

Yes, I did look in the More section - several times. No podcasts listed there - period. Not sure why.

In the More section I see my server and it’s libraries, my friend’s server and his libraries. Under Offline I see only Camera Roll, Downloads & Sync, and Open Video File.

Under Plex I see Movies & Shows, Live TV, Web Shows, News, and Music.

All I’m looking to do is get a podcast player that works with Android Auto and doesn’t skip to the next episode when I say FF!

You can install the beta manually since you have a Plex Pass. Since you are not in the actual beta program, you will only get the public version from the Play Store. So that’s all expected.

Can you provide a screenshot and the log from the app? Android, Android TV, Fire TV Logs | Plex Support

If I can install the beta manually 1) why did it fail to install unless I uninstalled the non-beta and 2) why did it report an old version number?

Repeating… Strange, this time it installed over the non-beta. Now have 8.8.0 21074 and now I have podcasts again!

Sh*t, tapping twice on my earbuds to go forward 30 seconds still skips past the entire podcast episode! When are they gonna fix that? Rarely does a podcast listener want to skip to the end of a podcast. I want to skip commercials and be able to rewind a few seconds to check what somebody just said. Plus, make the amount of seconds going forward and backward configurable.

The beta and public are still the same app. The main difference is how it is made available. The Play Store only allows installing the latest version of an app regardless if it’s public or beta. This allows the latest to install over the other.

I don’t believe the audio playback supports skipping within the track, only advance to the next track. This is the expected behavior for all Android apps. Headset Expected Behavior  |  Android Open Source Project

I understand about beta and public. However, this doesn’t change the fact that I downloaded the apk from the site listed, tried installing it and it said “Failed to install”. It was only after I uninstalled the public version and then re-attempted to install the beta apk that it actually installed. That’s what I was talking about.

When I tried to do this again however it worked. Strange.

I’m sorry but I’m not reading in that article the same thing you are. I do see it says that if you tap the button twice it should do “next”. What is not known is what “next” means. Next episode? Or next 30 seconds. Most podcast players interpret “Next” to be “Next 30 seconds”.

Add to that that the Plex app itself has a 10 second rewind and 30 second fast forward buttons on the face of the app right next to the Next and Prev episode buttons. Plus it’s interesting to note that even the link you provided says absolutely nothing about REW or Prev! Additionally, all podcast players I know wire REW/FF to button taps (2x and 3x) and do not wire Next and Prev episodes to any button.

All I’m asking for is the ability to configure the >> button as FF x seconds and the << button as REW y seconds and to be able to configure how many x seconds and y seconds. This should be the default for podcasts and configurable for music - I’m a guitarist and I often want to say to somebody riding in my car, “Did you hear that guitar part” and be able to rewind a few seconds to hear it again.

There are many times I’m listening to a podcast in my car on Android Auto and I want to skip the commercial so I hit FF and wham I’m at the next episode. There’s no way for me to go back to the episode I was listening to and then potentially having to scrub forward 1 hour and 10 minutes to get back to the point I was in the episode before I foolish hit FF expecting it to go forward 30 seconds without having to get off the highway, pull over and deal with my phone while not driving.

Download one of the other podcast apps like BeyondPod of PocketCasts or whatever. They all operate by skipping forward seconds not episodes.

I don’t know. Maybe some odd glitch.

But then how would you skip to the next track. You might not need it for podcasts but other might want it for regular music tracks.

Right, a regular podcast app that only expects podcasts is fine. If you used that to play music, I think you would get annoyed having to skip 3-s at a time through each song to get to the one you want.

With BeyondPod on Android Auto, for example, you’d tap the BeyondPod app and there is a button there to view the list of your unlistened to podcast episodes in your queue.

You can scroll up and down and search for the podcast you’d rather listen to. Generally the next podcast would be listed right after the currently playing one so you’d just tap that. It’s very easy and similar to how most music apps work too if you wish to play some other song (other than the next song). The point is that for podcasts you more likely are skipping commercials or rewinding the conversation back a few seconds because you weren’t paying attention. BTW, Audible for Android which plays audiobooks, also, by default, wires the FF/REW buttons to go forward/backward x seconds instead of skip to the next chapter or book.

IIRC you can tell podcast players like BeyondPod to see and play your music too. I suspect that the buttons would act similarly.

In any event, Plex knows if you are listening to music or podcasts so it can easily make the buttons work the way I want for podcasts and skip to the next song for music.

BTW, for music, I’d prefer a tap and hold to scrub forward or backward through the music. I know tap and hold is supposed to activate the Assistant but really, using the Assistant in a noisy car is usually kinda worthless and I already have a Push to Talk button in my vette that activates the assistant.

And I understand the desire to follow usage guidelines from Google about how an Android App should operate and by all means, configure it that way by default. But there is much worth in allowing users to program these little configurations to get a lot more out of their own usage models.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.