bug (YT Music) : Disable Music Video In Album is causing unintended playback behaviour in Top Songs page (full list) of any artist.

[Aryan-Chauhan]

Type

Error at runtime

Tools used

RVX Manager

Application

YT Music v8.05.51

Patches v5.4.2

Bug description

This bug happens if Disable Music Video In Album is enabled and it doesn't happen if the same feature is disabled.

Go to any artist's homepage, there you will see Top Songs by that artist. You have to open the Top Songs list in full view, this bug doesn't happen in short view of Top Songs.

Now play any song other than the No. 1 song.

You will notice that no matter what song you click on, the app will start playing only the No. 1 song of the Top Songs list.

Screen recording is attached below.

2025-03-14_18-55-01.mp4

Error logs

No logs.

Solution

There should be no unintended playback of songs, only intended playback of songs should happen.

Additional context

No additional context.

Device Environment

Android 12 (Realme UI 3.0)

Realme 7 Pro

Acknowledgements

• This issue does not reproduce on unpatched YouTube or YT Music.
• This issue is not a duplicate of an existing bug report.
• I did not use any settings marked as Experimental Flags.
• I have patched the APK according to the documentation.
• I have chosen an appropriate title.
• All requested information has been provided properly.
• I have written the title and contents in English.

[AkshayKanathur]

Check with 5.4.2-dev.1. It is the last version where yt music works fine. Disable music video in the album had a modification in 5.4.2-dev.2 and it's causing that issue. You can exclude that patch in new patch releases and it will work without that issue (temporary solution for using till the issue gets patched)

[AkshayKanathur]

I am getting another kind of issue because of this patch. If i try to play any song from an artist's page, other songs there should be added to the queue. Instead of that, i am getting a "logged in as (username)" pop-up and the queue will be broken.

Excluding that patch can fix that issue in new releases.

That issue started after 5.4.2-dev.2 because of a modification done in that patch.

Patch 5.4.2-dev.1 and previous releases don't have that bug.

[Aryan-Chauhan]

Yes, sometimes I also get that popup.

Sometimes, not always.

[AkshayKanathur]

@inotia00 My issue is still there.

[inotia00]

Is the issue still persisting even after patching with revanced-patches-5.5.1-dev.3?

[AkshayKanathur]

Is the issue still persisting even after patching with revanced-patches-5.5.1-dev.3?

Yes

[inotia00]

If so, this is not a duplicate issue.
You can continue the discussion in: #2838.

[Aryan-Chauhan]

After upgrading to patches v5.5.1-dev.3, my issue is solved.

Thanks for the quick fix!

[AkshayKanathur]

If so, this is not a duplicate issue.
You can continue the discussion in: #2838.

Thank you @inotia00 . My issue got fixed.

[AkshayKanathur]

You may close this issue since it is fixed.

[Aryan-Chauhan]

When the issue is solved in dev patches, inotia00 keeps the issue open.

When the same solution gets rolled out in a stable patch, then inotia00 closes the issue.

[AkshayKanathur]

Okay. Got it.

…

On Sat, Mar 15, 2025, 8:17 PM Aryan Chauhan ***@***.***> wrote: When the issue is solved in dev patches, inotia00 keeps the issue open. When the same solution gets rolled out in a stable patch, then inotia00 closes the issue. — Reply to this email directly, view it on GitHub <#2835 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A27OSPOW2AJHGO45ZN4YIB32UQ4QDAVCNFSM6AAAAABZAXTWRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRWGY4DOOJRG4> . You are receiving this because you commented.Message ID: ***@***.***> [image: Aryan-Chauhan]*Aryan-Chauhan* left a comment (inotia00/ReVanced_Extended#2835) <#2835 (comment)> When the issue is solved in dev patches, inotia00 keeps the issue open. When the same solution gets rolled out in a stable patch, then inotia00 closes the issue. — Reply to this email directly, view it on GitHub <#2835 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A27OSPOW2AJHGO45ZN4YIB32UQ4QDAVCNFSM6AAAAABZAXTWRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRWGY4DOOJRG4> . You are receiving this because you commented.Message ID: ***@***.***>

[AkshayKanathur]

I closed mine anyway since it's a duplicate. Fine right?

[inotia00]

Reflected in revanced-patches-5.5.1