bug: Updating with Latest RVX Patch makes SponsorBlock show wrong or bugged stats

[FishAndFire]

Type

Error at runtime

Tools used

RVX Manager

Application

YouTube v19.05.36 & v19.07.40

Bug description

After updating YouTube with Latest patch the SponsorBlock shows wrong stats
Before

After

Error logs

Solution

No response

Additional context

No response

Device Environment

Android 13, OneUI5.1
Android 14, OneUI6.1

Acknowledgements

• This issue does not reproduce on unpatched YouTube or YT Music.
• This issue also does not reproduce on original ReVanced Youtube or Revanced YT Music.
• This issue is not a duplicate of an existing bug report check here.
• 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.

[FishAndFire]

I wanted to add the screenrecording but for some reason github is showing "Failed to upload" and won't let me add it so I added screencaps from the screenrecording instead.

[risjsnx]

I wanted to add the screenrecording but for some reason github is showing "Failed to upload" and won't let me add it so I added screencaps from the screenrecording instead.

Try changing the json file in sponsorblock import/export setting
"skipCount": desired skipped segments, "minutesSaved": desired saved minutes from using sponsorblock,
But this only changed the local file not the server file

[FishAndFire]

But this only changed the local file not the server file

The problem is not with the server, like I mentioned I used two different devices with different app versions, when I noticed this I waited 2 days before updating the app on the second device and in the meantime I created new segments in SponsorBlock using the first device and while the stats are being updated normally on the second device, the first device was still showing bugged stats, not only that, while submitting a new segment the confirmation window shows "0 seconds" here's screenshot

Although submissions are submitting correctly despite showing 0 seconds.

The problem is with the patch.

[risjsnx]

Try updating the app with the latest version 20.05.xx for the phone that have bugged sponsorblock

[risjsnx]

There are some changes to sponsorblock setting code (for displaying time saved) at version 5.12.1

[FishAndFire]

Try updating the app with the latest version 20.05.xx for the phone that have bugged sponsorblock

The problem persists

Screen_Recording_20251011_121922_ReVanced.Extended.mp4

[btncua]

There are some changes to sponsorblock setting code (for displaying time saved) at version 5.12.1

I have same, already using latest patches and recommended version of YouTube, maybe these changes caused this?

[inotia00]

Perhaps there was a refactoring of the settings in the latest patch, and it seems like the SponsorBlock settings are now formatted incorrectly (visual bug).

I don't actively submit SponsorBlock segments, so I'm not sure what the correct format should be.

Try exporting the SponsorBlock settings from RVX and importing them into the official ReVanced.

Can you attach a screenshot of what the SponsorBlock settings look like in the official ReVanced?

[FishAndFire]

@inotia00 in official revanced if I use only my private user ID then the stats section shows my username, how many segments I created and how much other people's time I've saved

Screen_Recording_20251014_150734_YouTube_1.mp4

But if I use import/export setting given in SponsorBlock to restore SponsorBlock settings, it only shows how many segments I've skipped and nothing else but even this Stat is wrong

Screen_Recording_20251014_151850_YouTube.mp4

[snarevox]

i would just like to add that i am also experiencing the same issue with rvx 20.05.46 on both inotia00 and anddea builds with latest patches, while vanilla revanced 20.14.43 is displaying stats correctly.

no idea if accurate or not, but gpt seems to think its a milliseconds vs. seconds time scaling conversion bug..