Is proguard configuration outdated ?

[jhengazuki]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I am aware that this issue is being opened for the NewPipe Extractor, NOT the app, and my bug report will be dismissed otherwise.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

v0.24.8

Steps to reproduce the bug

1. Update newpipe to 0.24.8
2. Build release apk with enable minifyEnabled

Expected behavior

See playlist

Actual behavior

Field browseId_ for S6.b not found. Known fields are [public static final S6.b S6.b.e, public static volatile x4.m S6.b.f]

Screenshots/Screen recordings

No response

Logs

No response

Additional information

Proguard rule is same as v0.24.6

-keep class javax.script.** { ; }
-keep class jdk.dynalink.* { ; }
-keep class org.mozilla.javascript. { ; }
-keep class org.mozilla.javascript.* { ; }
-keep class org.mozilla.javascript.engine.* { ; }
-keep class org.schabi.newpipe.extractor.timeago.patterns.* { ; }
-dontwarn org.mozilla.javascript.JavaToJSONConverters
-dontwarn org.mozilla.javascript.tools.*
-dontwarn javax.script.**
-dontwarn jdk.dynalink.**

[FineFindus]

Could you try building with TeamNewPipe/NewPipe#12469 and check if that solves it?

[jhengazuki]

@FineFindus Thank you very much, the problem has been solved