Server Version#: Version 1.80.3.4008-03daab12
Player Version#: Plex for Android 10.3.0.4568-beta
Plex is broken and can’t make Continue Watching for episodes
Please, what is happening, could you fix it ?
Would you be able to provide Android logs from your client? Also, could you give a brief description of what is happening? Continue watching seems to be working fine for me.
Hello @morganj , thank you for your concern.
I just came back home, but I can’t het the logs from my Shield
I enter http://10.3.0.4655:32500/logging but nothing happen…
Well, thats not a valid IP.
Server 1.32.7.7621
App 10.4.0.4738
I have the same problem on 3 devices (2 android TV and android phone)
Clear app data or reinstall the app do nothing.
Fo me Plex is not usable in this state, please help me solve this.
error from the android phone:
11-11 00:04:43.535 i: [WiFiLockBehaviour] Aquiring WiFi lock since playback was started.
11-11 00:04:43.541 i: [BatteryMonitorBehaviour] Starting playback with 3572000 µAh (90%).
11-11 00:04:43.542 i: [PictureInPictureBehaviour] Picture-in-picture is available and can be used.
11-11 00:04:43.550 i: [MediaSessionBehaviour] Updating state to PLAYING
11-11 00:04:43.550 i: [Player] onPlaybackStarted
11-11 00:04:43.550 i: [TranscodeSession] Media choice updated
11-11 00:04:43.550 i: [TranscodeSession] Updating session status
11-11 00:04:43.554 i: [ExoPlayer][EventLogger] isPlaying [eventTime=1.68, mediaPos=218.69, window=0, period=0, true]
11-11 00:04:43.558 i: [TranscodeSession] Direct Play
11-11 00:04:43.638 e: Error fetching https://<external-ip>.f66d54726d0f465297f1f183c699a9d3.plex.direct:<port>/playQueues?includeChapters=1&continuous=0&includeLoudnessRamps=1&repeat=0&type=video&shuffle=0&uri=server%3A%2F%2F986c9f6a7e3ba182f21719bb624505da436fa32c%2Fcom.plexapp.plugins.library%2Flibrary%2Fmetadata%2F662787&key=%2Flibrary%2Fmetadata%2F662787&X-Plex-Token=...tml>
11-11 00:04:43.639 e: [PlayQueueAPIHelperBase] Unable to create play queue
11-11 00:04:43.641 e: [DelayedPlayQueueBehaviour] Failed to fetch Play Queue
11-11 00:04:56.839 i: [HttpServer] /192.168.10.50:53102 - GET /logging
11-11 00:04:57.884 e: [MetricsSender] Error posting metrics.
11-11 00:04:57.889 e: An exception occurred: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
11-11 00:04:57.890 e: Stacktrace: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
at com.android.org.conscrypt.SSLUtils.toSSLHandshakeException(SSLUtils.java:356)
at com.android.org.conscrypt.ConscryptEngine.convertException(ConscryptEngine.java:1134)
at com.android.org.conscrypt.ConscryptEngine.readPlaintextData(ConscryptEngine.java:1089)
at com.android.org.conscrypt.ConscryptEngine.unwrap(ConscryptEngine.java:876)
at com.android.org.conscrypt.ConscryptEngine.unwrap(ConscryptEngine.java:747)
at com.android.org.conscrypt.ConscryptEngine.unwrap(ConscryptEngine.java:712)
at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.processDataFromSocket(ConscryptEngineSocket.java:896)
at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.-$$Nest$mprocessDataFromSocket(Unknown Source:0)
at com.android.org.conscrypt.ConscryptEngineSocket.doHandshake(ConscryptEngineSocket.java:236)
at com.android.org.conscrypt.ConscryptEngineSocket.startHandshake(ConscryptEngineSocket.java:218)
at okhttp3.internal.connection.RealConnection.connectTls(SourceFile:73)
at okhttp3.internal.connection.RealConnection.establishProtocol(SourceFile:53)
at okhttp3.internal.connection.RealConnection.connect(SourceFile:197)
at okhttp3.internal.connection.ExchangeFinder.findConnection(SourceFile:275)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(SourceFile:1)
at okhttp3.internal.connection.ExchangeFinder.find(SourceFile:53)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(SourceFile:32)
at okhttp3.internal.connection.ConnectInterceptor.intercept(SourceFile:12)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at okhttp3.internal.cache.CacheInterceptor.intercept(SourceFile:195)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at okhttp3.internal.http.BridgeInterceptor.intercept(SourceFile:171)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(SourceFile:35)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at nj.a.intercept(SourceFile:50)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at okhttp3.logging.HttpLoggingInterceptor.intercept(SourceFile:20)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at io.c.intercept(SourceFile:376)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:163)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(SourceFile:118)
at okhttp3.internal.connection.RealCall.execute(SourceFile:28)
at oj.f$c.i(SourceFile:48)
at oj.f$c.f(Unknown Source:0)
at oj.i.invoke(SourceFile:2)
at oj.f$c.g(SourceFile:107)
at oj.f$c.a(SourceFile:38)
at oj.k.run(SourceFile:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:308)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Caused by: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
at com.android.org.conscrypt.TrustManagerImpl.verifyChain(TrustManagerImpl.java:672)
at com.android.org.conscrypt.TrustManagerImpl.checkTrustedRecursive(TrustManagerImpl.java:549)
at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:505)
at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:425)
at com.android.org.conscrypt.TrustManagerImpl.getTrustedChainForServer(TrustManagerImpl.java:353)
at android.security.net.config.NetworkSecurityTrustManager.checkServerTrusted(NetworkSecurityTrustManager.java:94)
at android.security.net.config.RootTrustManager.checkServerTrusted(RootTrustManager.java:90)
at com.android.org.conscrypt.ConscryptEngineSocket$2.checkServerTrusted(ConscryptEngineSocket.java:163)
at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:260)
at com.android.org.conscrypt.ConscryptEngine.verifyCertificateChain(ConscryptEngine.java:1638)
at com.android.org.conscrypt.NativeCrypto.ENGINE_SSL_read_direct(Native Method)
at com.android.org.conscrypt.NativeSsl.readDirectByteBuffer(NativeSsl.java:569)
at com.android.org.conscrypt.ConscryptEngine.readPlaintextDataDirect(ConscryptEngine.java:1095)
at com.android.org.conscrypt.ConscryptEngine.readPlaintextData(ConscryptEngine.java:1079)
... 42 more
Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
... 56 more
11-11 00:05:27.840 e: [MetricsSender] Error posting metrics.
Same problem. After something is watched or marked as watched it very briefly pops up into the number one spot in continue watching but then disappears
I do notice that a lot of the content that is stuck there appears to be things I marked as watched manually after I created a new server
It also seems to change. My phone right now is showing items I watched a week ago, while my tablet is showing things I haven’t watched in months. This seems to flip flip any given day I check
The managed account I have also seems to work properly on all the devices mentioned
Only the admin account have this issue.
I had to re-add my libraries and bow it is working again (delete all files from Library/Application Support/Plex Media Server/Plug-in Support/Databases and add libraries via Plex web)
@morganj do the errors in the logs supplied give you any idea what might be happening?
I have my own, I can send in a pm if necessary. Thanks
There is not enough in the above logs to go on, would you be able to provide a full log if possible?
Thanks for the logs, we are still investigating and there is nothing that stands out from your logs.
Is anyone still experiencing the issue on 10.3.0? We disabled a feature that was to improve the loading of hubs on the homepage to see if this could be the cause. It is still enabled on 10.4.0 in case anyone is on the beta.
Still present on 10.3.0
Question…
This looking at an individual episode in the library. “View play history”
Is this normal to have it greyed out like this? I can hardly read it
It doesn’t look like that if I go to the play history in the dashboard
Also, some episodes I’ve watched show nothing in that view
Yet if I go to the Dashboard and click my profile “view play history” you can clearly see it there
All of the shows mentioned get fed to my continue watching on HTPC, Plex Web, and Plex for Windows without issue so it’s possibly just another unrelated issue. But I can’t help but wonder
That text does seem difficult to read. Looks that way for me as well. I can bring it up but I don’t think it’s related.
So basically no episodes are shown in CW, both next-up episodes and partially watched ones? What about partially watched movies?
And you see the episode in your profile watched history but when viewing the play history for it there is nothing?
What about episodes that you start watching on another client do they appear on Android CW?
fwiw, It seems the html for the row is a button tag and has a class of ‘isDisabled’ which then gets this css:
.isDisabled {
opacity: .2;
}
Yes, its known and will be fixed. Its apparently been around for some time.
I know this long but bear with me…
Up next, partially watched, movies or TV in all 10+ libraries were affected
Essentially Fire TV, tablet and phone all had the same items stuck in the continue watching.
The Fire TV had about 30 of the same shows stuck in the same spot. Phone had over 50 and the tablet had about 20.
I have 2 servers that had this issue but it affected all android devices and only android devices
That was somewhat odd to me since the bugs I’ve experienced in the past have had a clear line in the sand between android TV and android Mobile
If you noticed I said “had this issue”
Here’s what I found.
I had my Weeks to consider for Continue watching set to 120
Maximum number of continue Watching items which will appear set to 200
It did not seem to honor the setting at 200. I did a rough count and there were 270 items so it appears as though the old items were not falling off the back like I believe they should
Here’s what I did and I’m not sure what step fixed it but for anyone having the same issue follow these steps
-
Weeks to consider for Continue Watching - Lowered from 120 down to 60
-
Maximum number of Continue Watching items which will appear. - Lowered from 200 down to 100
-
Disabled - Include season premieres in Continue Watching
(many of the items stuck seemed to be related to this, i.e. s02e01 of a series) -
(Plex for Windows) - Debug → Restore Defaults → Re-pin libraries
-
On every single android client you have - Reset All Customizations → Re-pin libraries
-
Put away the gun you were about to shoot yourself in the face with
After doing all of this the continue watching is uniform across all devices and appears to be adding newly watched items from any library
Also, the example above, Loki s01e01 episode with “Nothing to see here” now displays the correct watch history
I’m not sure this is a solution or workaround because my continue watching now has 91 episodes. When it reaches the 100 limit I set, I’m afraid this is going to happen again
Honestly, I spend more time than most reading problems and solutions here in the forum as well as tinkering with this app
Your casual daily user or novice would have almost no chance of fixing something like this. They would nuke their server like myakove did or become the next “I’m moving to Jellyfin” guy
Through my great luck and fortune, I happen to get affected by these issues long before I see a swarm of other people here 8 months later having the same problem. Please look into this before that happens
Thanks
So you are saying you had over the amount of max number in continue watching? I have tried replicating that now but it always removes the last item in the list when adding a new one.
That appears to be the case. This is what I had originally
As I scrolled from the beginning to end of my continue watching I had a rough count of 270-ish shows
I know it says if you set the value too high you can experience performance issues but I’m not sure exactly what that means or what is “too high”. I assumed that mean you may get some posters that are slow to load or items wouldn’t be as responsive. If this is somehow a symptom of that, then there should be a hard limit to the value you can set
I rebuilt this server after a drive failure. I manually marked a large majority of items as watched to replicate what I had on my now backup server
The items that were manually marked as watched seemed to be most of the items that just got stuck towards the front of continue watching with the same “watched on date”
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
