Continue watching resume issue

Server Version#: 1.22.1.4275
Player Version#: 8.15.0

Select a film to continue watching and then resume. Playback starts from the beginning rather than where it was previously stopped. Strangely, if you stop and resume again, the playback starts from the correct place. This was not an issue in 8.13.1 (last known available version from Amazon Appstore without the issue).

2 Likes

Same issue here.

Duplicate: Resume starts from beginning on Fire Stick

My duplication steps:

  1. Start with 2 different Fire Sticks or Fire TVs
  2. Start a video on FS1, exit.
  3. On FS2, attempt to resume the same video from ā€œContinue Watchingā€. The video starts from the beginning instead of where it left off from FS1.
  4. Still on FS2, back out and attempt to resume playback from ā€œContinue Watchingā€ again. After a delay, this time it works resuming from where FS1 originally left off.

Happens every time since a recent update.

can anyone else confirm if @Plexifier80 reply is linking you back to this thread

just like the resume option is not working…

I’ve tried copying and pasting linked URI: Resume starts from beginning on Fire Stick

no change, new browser/incognito/in private, same issue

I’ve been trying to reproduce this internally, but haven’t had much luck, I’m afraid. Can someone please reproduce this, and then provide some logs from the Fire TV, please?

Same issue here.

Fire Plex app v8.15.0
Media server v1.22.2.4282

Happens to me as well. Every time I ā€˜resume’ it reboots my plex app. I’ll see if I can get some logs.

1 Like

Also getting issue will try and get logs

Sideloading version 8.14.1 does make resume work properly again.

Just out of interest, which fire tv devices are people using here?

Happens here as well. Happens on 4K Fire Stick and Insignia Fire TVs

I have the same issue. Firestick OS 5.2.7.8
The time remaining showccorrectly, but when I resume, it always reverts to the start. Even if I back out and try again it restarts.
Not sure how to get logs, so I am hoping someone else can do it!

This same thing is happening to me. I also can’t use the seek bar to get back to where I left off. So can’t resume and can’t seek to my previous location. I can use the 30 forward 10 back buttons, but not the slider. I have the most recent fire tv client running Plex version 8.16.1.24597. 2nd gen fire to stick. Server version 1.22.3.4392.

Do you have any luck getting logs and find where maybe the issue is? I have similar issue with resume not working most of the time. And when it worked, it would crash the player after a few minutes of playing. I found this in the log and I am guessing this caused the app to restart?

05-02 13:45:26.854 e: An exception occurred: java.lang.IllegalArgumentException: Invalid URL port: ā€œ0ā€
05-02 13:45:26.863 e: Stacktrace: java.lang.IllegalArgumentException: Invalid URL port: ā€œ0ā€
at okhttp3.HttpUrl$Builder.parse$okhttp(SourceFile:34)
at okhttp3.HttpUrl$Companion.get(SourceFile:1)
at okhttp3.Request$Builder.url(SourceFile:7)
at com.plexapp.plex.net.pms.sync.f.x(SourceFile:21)
at com.plexapp.plex.net.pms.sync.f.w(SourceFile:2)
at com.plexapp.plex.net.pms.sync.p.H(SourceFile:2)
at com.plexapp.plex.net.pms.sync.p.t(SourceFile:6)
at com.plexapp.plex.net.pms.sync.f.o(SourceFile:3)
at com.plexapp.plex.net.pms.g0.s(SourceFile:8)
at org.jboss.netty.channel.p0.d(SourceFile:2)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline$a.a(SourceFile:2)
at g.a.a.c.c.d.d(SourceFile:7)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline$a.a(SourceFile:2)
at g.a.a.c.a.a.g.s(SourceFile:16)
at org.jboss.netty.channel.p0.d(SourceFile:2)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline$a.a(SourceFile:2)
at org.jboss.netty.channel.v.r(SourceFile:1)
at org.jboss.netty.handler.codec.replay.b.C(SourceFile:8)
at org.jboss.netty.handler.codec.replay.b.u(SourceFile:11)
at org.jboss.netty.handler.codec.replay.b.s(SourceFile:9)
at org.jboss.netty.channel.p0.d(SourceFile:2)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline.a(SourceFile:3)
at org.jboss.netty.channel.v.q(SourceFile:1)
at org.jboss.netty.channel.v.p(SourceFile:1)
at org.jboss.netty.channel.u0.f.l.i(SourceFile:16)
at org.jboss.netty.channel.u0.f.l.g(SourceFile:5)
at org.jboss.netty.channel.u0.f.l.run(SourceFile:13)
at g.a.a.e.g.run(SourceFile:7)
at g.a.a.e.k.e$a.run(SourceFile:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)

05-02 13:45:26.866 e: An exception occurred: java.lang.IllegalArgumentException: Invalid URL port: ā€œ0ā€
05-02 13:45:26.872 e: Stacktrace: java.lang.IllegalArgumentException: Invalid URL port: ā€œ0ā€
at okhttp3.HttpUrl$Builder.parse$okhttp(SourceFile:34)
at okhttp3.HttpUrl$Companion.get(SourceFile:1)
at okhttp3.Request$Builder.url(SourceFile:7)
at com.plexapp.plex.net.pms.sync.f.x(SourceFile:21)
at com.plexapp.plex.net.pms.sync.f.w(SourceFile:2)
at com.plexapp.plex.net.pms.sync.p.H(SourceFile:2)
at com.plexapp.plex.net.pms.sync.p.t(SourceFile:6)
at com.plexapp.plex.net.pms.sync.f.o(SourceFile:3)
at com.plexapp.plex.net.pms.g0.s(SourceFile:8)
at org.jboss.netty.channel.p0.d(SourceFile:2)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline$a.a(SourceFile:2)
at g.a.a.c.c.d.d(SourceFile:7)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline$a.a(SourceFile:2)
at g.a.a.c.a.a.g.s(SourceFile:16)
at org.jboss.netty.channel.p0.d(SourceFile:2)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline$a.a(SourceFile:2)
at org.jboss.netty.channel.v.r(SourceFile:1)
at org.jboss.netty.handler.codec.replay.b.C(SourceFile:8)
at org.jboss.netty.handler.codec.replay.b.u(SourceFile:11)
at org.jboss.netty.handler.codec.replay.b.s(SourceFile:9)
at org.jboss.netty.channel.p0.d(SourceFile:2)
at org.jboss.netty.channel.DefaultChannelPipeline.u(SourceFile:1)
at org.jboss.netty.channel.DefaultChannelPipeline.a(SourceFile:3)
at org.jboss.netty.channel.v.q(SourceFile:1)
at org.jboss.netty.channel.v.p(SourceFile:1)
at org.jboss.netty.channel.u0.f.l.i(SourceFile:16)
at org.jboss.netty.channel.u0.f.l.g(SourceFile:5)
at org.jboss.netty.channel.u0.f.l.run(SourceFile:13)
at g.a.a.e.g.run(SourceFile:7)
at g.a.a.e.k.e$a.run(SourceFile:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)

And for the not resume, I am guessing it is this?

05-02 13:45:35.062 i: [FFmpeg] [ERROR] [tls @ 0xb7e18820] Error decoding the received TLS packet.

05-02 13:45:35.064 i: [FFmpeg] [WARN] [https @ 0xb7adf8f0] Will reconnect at 81084416 in 0 second(s), error=I/O error.

and/or

05-02 13:45:34.424 i: [FFmpeg] [ERROR] [tls @ 0xb7befdd0] Error in the pull function.

05-02 13:45:34.427 i: [FFmpeg] [WARN] [https @ 0xb7adf8f0] Will reconnect at 78512128 in 0 second(s), error=I/O error.

Thank you in advance.

We’ve got what we need already, thanks :slight_smile:

Have sideloaded version 8.17.0.25084-beta and the issue appears to be resolved.

Do we have any update as to when this will be resolved? I have 6x fire cube devices in my home all which have the same issue. Resume always sends it to the beginning of the show or outright crashes the player.

I don’t have an ETA, I’m afraid :disappointed:

Is there any workarounds instead of side loading a beta version of code?

I believe if you press back again, and then try to resume it again, it should resume correctly, which is annoying I know, but we’re working on it.

You will probably have already found that this matter was resolved in Plex for Android 8.17.0. Although, Plex describe the issue as ā€˜resuming did not always set the correct offset’.

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