Seeking (by dragging the play position) frequently marks the episode as played

[RalfJung]

Checklist

• I have used the search function for OPEN issues to see if someone else has already submitted the same bug report.
• I have also used the search function for CLOSED issues to see if the problem is already solved and just waiting to be released.
• I will describe the problem with as much detail as possible.
• If the bug only to occurs with a certain podcast, I will include the URL of that podcast.

App version

3.3.2

Where did you get the app from

F-Droid

Android version

Android 12 (LineageOS)

Device model

Moto G7 Power

First occurred

Years ago

Steps to reproduce

It's not fully reproducible, but it happened many times now:

• start playing an episode
• in the playback screen (that shows the time progress bar indication the position in the podcast), drag the "current position" indicate around (to skip the first ~10min of the podcast)

Expected behaviour

The podcast should jump to the given position.

Current behaviour

Every now and then (maybe around 10% of the time), the playback screen just closes and AntennaPod jumps to the episode list for this podcast. In this case the episode is marked as played and deleted from the device.

This is quite frustrating as I now have to adjust the episode filter to show already played episodes, find the affected episode, mark it as unplayed, start downloading the episode again, and set the filter to "unplayed" again.

I think what happens is that somehow the "current position" marker jumps to the end of the episode, and hence it is considered finished. Maybe it is losing track of my finger and somehow that is interpreted as sweeping all the way to the right? For some time I thought it would help to never start dragging from position 0, so I always used the "seek" button to seek 10-30s and only then did the drag-n-drop of the "current position" slider, but that doesn't seem fully reliable either. I am not particularly clumsy and I don't have trouble with incorrect inputs in other applications, so I would hope that is some way to avoid this kind of misinterpretation. As a developer myself, I also understand that this is a terrible to debug issue, given that you likely never encountered it yourself.

Logs

No response

[tonytamsf]

I am curious if this happens with any of your other devices? It is at all possible your screen has a glass fault/crack?

[RalfJung]

I only have one device. The screen is completely healthy, no visual signs of any damage.