Is proguard configuration outdated ?
Checklist
- [x] I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
- [x] I am aware that this issue is being opened for the NewPipe Extractor, NOT the app, and my bug report will be dismissed otherwise.
- [x] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [x] This issue contains only one bug.
- [x] I have read and understood the contribution guidelines.
Affected version
v0.24.8
Steps to reproduce the bug
- Update newpipe to 0.24.8
- 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.**
Could you try building with https://github.com/TeamNewPipe/NewPipe/pull/12469 and check if that solves it?
@FineFindus Thank you very much, the problem has been solved