Audio playback interruption on Android devices

[yelkamel]

Description

We're experiencing an issue with audio playback on Android devices using the just_audio package. The problem appears to be affecting only some users and is not reproducible in development or release modes on our test devices.

Symptoms

• Audio playback stops unexpectedly during meditation sessions or while playing sleep music
• The issue occurs at random times, not consistently at the same timestamp
• When playback stops, users can see the progress bar moving but hear no sound
• Attempting to restart playback results in the progress bar moving without audio
• Some users report seeing a "Connection error" message when the interruption occurs
• The problem persists whether the screen is locked or unlocked
• The issue happens both when the app is in the foreground and background

Additional Information

• This issue is only reported on Android devices
• The problem started occurring recently, but the app was working fine before
• We've verified it's not a memory leak issue
• Affected users seem to have sufficient RAM available (based on crash analytics data)
• No crashes are reported in our crash analytics related to this issue
• The problem occurs for both short and long audio files

Steps to Reproduce

Unfortunately, we haven't been able to reproduce this issue consistently in our development or testing environments. It seems to only affect certain users in production.

Expected Behavior

Audio should play continuously without interruption for the entire duration of the meditation or sleep music track.

Current Behavior

Audio playback stops unexpectedly, and users are unable to resume playback from the point of interruption.

Environment

• Flutter version: [Please specify]
• just_audio version: [Please specify]
• Android version: Various (issue reported on multiple Android versions)
• Device models: Various Android devices

Additional Context

We've attempted to debug this issue but have been unsuccessful due to its inconsistent nature and inability to reproduce it in controlled environments. Any insights or suggestions for further debugging or potential causes would be greatly appreciated.

[github-actions[bot]]

Oops, it appears that your issue did not follow the template and is missing one or more required sections. Please open a new issue, and provide all required sections and information.

FAQ:

1. Do I really need to submit a minimal reproduction project for a bug? A: Yes. I prioritise bugs secondarily on how many people are affected, and primarily on whether the bug report is complete, in the sense that it enables me to immediately reproduce it and start working on a fix. If a bug is important to you, the best thing you can do is to provide all requested information ASAP so that I can start looking into it ASAP.

2. I think I supplied all required information, so did the bot make a mistake? A: The bot only checks the section headings, so when you post a new issue, make sure you leave the section headings intact. (Note that because of this, it is even possible to trick the bot by including only the section headings, and then not providing the requested information under each heading. This is frowned upon, and the issue will be closed manually.)