The playback of streamed episodes regularly jumps backwards or forwards

[PCigales]

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

Google Play

Android version

Oreo 8.0

Device model

Samsung Galaxy A8 (SM A-530F)

First occurred

Since the beginning of the utilization of the app

Steps to reproduce

1. Suscribe to https://feed.ausha.co/oakmehzx9Dp2
2. Listen one or two episodes by streaming the audio content

Expected behaviour

The episode should be played in a continuous way (I have been listening to this podcast for years with Google Podcast without any issue).

Current behaviour

About every other time, during the playback, the player jumps unexpectedly either backwards or forwards for a dozen seconds, and in the first case, stops before having reached the end of the episode. Attempting to use the seek bar leads more often that not the player to hang until the app is force closed.

I suspect it is due to the dynamic advertising insertion happening at the beginning of the stream, which causes the offset with the timestamps. Battery optimizations are all disabled for AntennaPod.
I do not know how the app streams the content and send its requests to the server, but the reason may be that repeated range requests are used, rather than one with just the start position, and any session identifier assigned the first time is not sent back, and that the total size declared in the range header of the response, if chunked transfer encoding is not used, is ignored, as it could otherwise be used to recalculate the right byte range.
Rather than fixing the way the media content is retrieved, as the app seems to rely on a third party solution, a workaround would be to cache the whole data in memory at start, when its size does not exceed a user defined threshold (it is a matter of not more than 30 MB for a half an hour episode).
Of course, each episode could first be manually downloaded by the user before being played, but that implies several manipulations. The option to activate automatically download of each new released episode is not satisfactory when only a few ones among all of them are indeed listened.

Thanks in advance.

Logs

No response