[widevine][android] Fix problem with hardcoded class names on jni objects#2007
[widevine][android] Fix problem with hardcoded class names on jni objects#2007CastagnaIT merged 4 commits intoxbmc:Piersfrom
Conversation
this is now used to construct class path to android objects such as listeners
ReviewCritical — Dependency points to personal fork branch Must Fix — |
📝 Kodiai Draft Review Summary
What ChangedFixes JNI class name construction for repackaged Kodi builds by re-enabling Reviewed: core logic, docs Strengths
ObservationsImpact[CRITICAL] depends/android/libandroidjni/libandroidjni.txt (1): Dependency uses mutable branch reference Suggestions
Verdict🔴 Address before merging -- 1 blocking issue(s) found (CRITICAL/MAJOR) Review Details
|
fb299d5 to
be3468d
Compare
|
Must Fix - Two issues with the dependency reference that need to be resolved before merging: 1. SHA256 is the hash of an empty file ( 2. Dependency points to a personal fork branch ( The |
|
@kodiai please review |
kodiai responseDecision: NOT APPROVED Issues:
|
|
@kodiai please review PR, without take in account BOT comments that are outdated and wrong |
kodiai responseWrite mode is disabled for this repo. Update write:
enabled: trueThen re-run the same |
|
@kodiai please review without take in account BOT comments that are outdated and wrong |
Description
this depends on PRs:
xbmc/libandroidjni#56
xbmc/xbmc#27944
on jni dependency there was hardcoded class names
which although they work for a regular kodi build, it do not work if the Kodi package is renamed with a different name
this will allow you to build a class name based on the actual package name
it is a regression from PR #1988
the old custom ISA JNI code already did this, but i didn't grasp the concept because on the JNI library already contained a listener with a hardcoded class name
Motivation and context
fix #1997
How has this been tested?
Screenshots (if appropriate):
Types of change
Checklist: