Proguard rules for Android release builds

Open Beginner friendly
#215 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, java
Domain
build-system, mobile

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.

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");
Dominant language
Java
Stars
333
Forks
68
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uber/h3-java

All issues in uber/h3-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.