All Projects → RikkaApps → HiddenApiRefinePlugin

RikkaApps / HiddenApiRefinePlugin

Licence: MIT license
A Gradle plugin that improves the experience when developing Android apps, especially system tools, that use hidden APIs.

Programming Languages

java
68154 projects - #9 most used programming language
kotlin
9241 projects

Labels

HiddenApiRefinePlugin

A Gradle plugin that improves the experience when developing Android apps, especially system tools, that use hidden APIs.

Background

When developing system tools, it's inevitable to use hidden APIs. There are two ways to use hidden APIs, the reflection way and the linking way. For some types of system tools, a large amount of hidden APIs is required, using the reflection way is too inconvenient. So the linking way is commonly used in those projects.

In short, the linking way is to create Java-only modules with stub classes and then compileOnly them in the main Android modules. This is the same as what Android SDK's android.jar does.

However the linking way, or "the stub way", have some problems:

  1. "Bridge classes" is required if only some members of the class are hidden.
  2. Kotlin will try to link public classes from the stub module, implementation a second Java-only which compileOnly the stub module can workaround the problem.
  3. Interface implementation will be removed by R8 if the stub module is not compileOnly directly from the main module, however doing this will bring back problem 2.

This plugin is to solve these problems.

What do this plugin do

This plugin uses the Transform API of the Android Gradle Plugin to create a transform that modifies class names, the names are user specified by annotation @RefineAs. So that all the problems will be gone and the stub module does not need to be a Java-only module.

The idea and the implementation is from @Kr328.

Usage

gradle-plugin annotation-processor annotation runtime

Replace all the <version> below with the version shows here.

Create "hidden-api" module

  1. Create a new Android library module

  2. Add annotation dependency

    dependencies {
        annotationProcessor 'dev.rikka.tools.refine:annotation-processor:<version>'
        compileOnly 'dev.rikka.tools.refine:annotation:<version>'
    }
  3. Add the hidden classes

    Here, we use a hidden PackageManager API as the example.

    package android.content.pm;
    
    import dev.rikka.tools.refine.RefineAs;
    
    @RefineAs(PackageManager.class)
    public class PackageManagerHidden {
        public interface OnPermissionsChangedListener {
            void onPermissionsChanged(int uid);
        }
    
        public void addOnPermissionsChangeListener(OnPermissionsChangedListener listener) {
            throw new RuntimeException("Stub!");
        }
        public void removeOnPermissionsChangeListener(OnPermissionsChangedListener listener) {
            throw new RuntimeException("Stub!");
        }
    }

    This line @RefineAs(PackageManager.class) will let the plugin renames android.app.PackageManagerHidden/android.app.PackageManagerHidden.OnPermissionsChangedListener to android.app.PackageManager/android.app.PackageManager.OnPermissionsChangedListener.

Use hidden API

  1. Apply this plugin in the final Android application module

    plugins {
        id('dev.rikka.tools.refine') version '<version>'
    }
  2. Import "hidden-api" module with compileOnly

    dependencies {
        compileOnly project(':hidden-api')
    }
  3. Import the "Refine" class (Optional, if you don't need the "unsafeCast" method)

    dependencies {
        implementation("dev.rikka.tools.refine:runtime:<version>")
    }
  4. Use the hidden API

    Refine.<PackageManagerHidden>unsafeCast(context.getPackageManager())
                 .addOnPermissionsChangeListener(new PackageManagerHidden.OnPermissionsChangedListener() {
                     @Override
                     public void onPermissionsChanged(int uid) {
                         // do staff
                     }
                 });

    After R8, this "cast" will be "removed" or "inlined". This line will be identical to a normal method call.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].