Proguard rules for Android release builds
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 333
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
As the native code is referring to Java classes by reflection, could the library com.uber:h3-android also expose pro guard rules for R8 release android app builds?
jclass local_latLngClass =
(**env).FindClass(env, "com/uber/h3core/util/LatLng");
jclass local_h3eClass =
(**env).FindClass(env, "com/uber/h3core/exceptions/H3Exception");
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how the com.uber:h3-android library is packaged and where consumer ProGuard or R8 rules can be exposed. Use the shown reflective FindClass references for LatLng and H3Exception as the cases to verify. Done means an Android release build using R8 retains and can load those classes without runtime failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100