Telegram for Android does not respect topic boundaries when creating audio playback queues in groups with Topics enabled.
When playing an audio file from a specific topic, the playback queue incorrectly includes tracks from the entire group instead of restricting the queue to the originating topic. This affects the playback queue itself, regardless of whether Shuffle is enabled or disabled.
The same issue previously existed in Telegram Desktop but has already been fixed there. Desktop now correctly maintains topic-specific playback queues, while Telegram for Android still exhibits the incorrect behavior.
As a result, individual topics cannot be reliably used as independent playlists for music, podcasts, or other audio collections.
Steps to reproduce
Create a group and enable Topics (forum mode).
Create at least two separate topics (e.g., "Playlist A" and "Playlist B").
Upload several audio files to each topic, ensuring that each contains different tracks.
Open "Playlist A" in Telegram for Android.
Start playing an audio file from that topic.
Tap the music player to expand the playback queue.
Observe that the queue includes tracks from the entire group instead of only "Playlist A".
Repeat the test with Shuffle both enabled and disabled.
Current result
The playback queue includes audio tracks from all topics in the group instead of being restricted to the topic from which playback was started. Consequently, Next, Previous, and other playback controls can operate across unrelated topics.
The issue persists regardless of whether Shuffle is enabled or disabled.
Expected result
The playback queue should include only audio tracks from the topic in which playback was started. Next, Previous, and other playback controls should remain within that topic's queue, consistent with the existing behavior in Telegram Desktop.
The Android team should investigate how the playback queue is initialized and scoped to the originating topic and align its behavior with the Desktop implementation.