Getting Started
Version restrictions¶
Minimum Gradle version: 7.6👇 (supports 8.0 and above)
Minimum SDK version: minSdkVersion >= 21
Steps for usage¶
Can you give the project a Star before starting? Thank you very much, your support is my only motivation. Stars and Issues are welcome!
The repository address of this library is in Maven central. If you cannot get the dependent package, please put the mirror address such as Alibaba after mavenCentral()
1. Introduce the plug-in, choose one of the two methods below (required)¶
Method 1: apply
method¶
Depend on the plug-in in build.gradle
in the project root directory
-
Using the plugins DSL:
plugins { //👇Required item (1)👈 apply is set to true to automatically apply debugMode to all modules, if false, follow step 5 below. id "io.github.FlyJingFish.AndroidAop.android-aop" version "2.3.0" apply true }
- If you have the
com.google.dagger.hilt.android
plugin in your project, put this plugin before it.
- If you have the
-
Using legacy plugin application:
buildscript { dependencies { //👇equired items (1)👈 classpath "io.github.FlyJingFish.AndroidAop:android-aop-plugin:2.3.0" } } //👇Add this sentence to automatically apply debugMode to all modules. If not, follow step 5 below. apply plugin: "android.aop"
- If you have the
com.google.dagger:hilt-android-gradle-plugin
plugin in your project, put this plugin before it.
- If you have the
-
Using the plugins DSL:
plugins { //👇Required item (1)👈 apply is set to true to automatically apply debugMode to all modules, if false, follow step 5 below. id("io.github.FlyJingFish.AndroidAop.android-aop") version "2.3.0" apply true }
- If you have the
com.google.dagger.hilt.android
plugin in your project, put this plugin before it.
- If you have the
-
Using legacy plugin application:
buildscript { dependencies { //👇Required items (1)👈 classpath("io.github.FlyJingFish.AndroidAop:android-aop-plugin:2.3.0") } } //👇Add this sentence to automatically apply debugMode to all modules. If not, follow step 5 below. apply(plugin = "android.aop")
- If you have the
com.google.dagger:hilt-android-gradle-plugin
plugin in your project, put this plugin before it.
- If you have the
Note
If you use the hilt plugin in your project, pay attention to the order of importing plugins mentioned in the article (click the "+" above to see more information)
Add in build.gradle
of app
-
Using the plugins DSL:
-
Using legacy plugin application:
Warning
id 'android.aop'
should be placed at the last line, especially after id 'com.android.application'
or id 'com.android.library'
Method 2: plugins
method¶
plugins
method- Add directly to
build.gradle
of app
2. If you need to customize aspects, and the code is Kotlin
(optional)¶
- Depend on the plug-in in
build.gradle
in the project root directory
List of matching version numbers for Kotlin and KSP Github
3. Introduce dependent libraries (required)¶
plugins {
//Optional 👇, if you need to customize aspects and use the android-aop-ksp library, you need to configure it
id 'com.google.devtools.ksp'
}
dependencies {
//👇Required items
implementation "io.github.FlyJingFish.AndroidAop:android-aop-core:2.3.0"
//👇Optional (1)👈 This package provides some common annotation aspects
implementation "io.github.FlyJingFish.AndroidAop:android-aop-extra:2.3.0"
//👇Required item If you already have this item in your project, you don’t need to add it.
implementation "androidx.appcompat:appcompat:1.3.0" // At least in 1.3.0 and above
//👇Optional (2)👈Click + to view detailed description, ⚠️supports aspects written in Java and Kotlin code
ksp "io.github.FlyJingFish.AndroidAop:android-aop-ksp:2.3.0"
//👇Optional (3)👈Click + to view detailed description, ⚠️only applies to aspects written in Java code
annotationProcessor "io.github.FlyJingFish.AndroidAop:android-aop-processor:2.3.0"
//⚠️Choose one of the above android-aop-ksp and android-aop-processor
}
- This library has built-in annotations for some functions defined using @AndroidAopPointCut
- When you use the five custom aspect annotations introduced here, it means that you must choose one from
android-aop-ksp
andandroid-aop-processor
as a required option - When you use the five custom aspect annotations introduced here, it means that you must choose one from
android-aop-ksp
andandroid-aop-processor
as a required option
plugins {
//Optional 👇, if you need to customize aspects and use the android-aop-ksp library, you need to configure it
id("com.google.devtools.ksp")
}
dependencies {
//👇Required items
implementation("io.github.FlyJingFish.AndroidAop:android-aop-core:2.3.0")
//👇Optional (1)👈 This package provides some common annotation aspects
implementation("io.github.FlyJingFish.AndroidAop:android-aop-extra:2.3.0")
//👇Required item If you already have this item in your project, you don’t need to add it.
implementation("androidx.appcompat:appcompat:1.3.0") // At least in 1.3.0 and above
//👇Optional (2)👈Click + to view detailed description, ⚠️supports aspects written in Java and Kotlin code
ksp("io.github.FlyJingFish.AndroidAop:android-aop-ksp:2.3.0")
//👇Optional (3)👈Click + to view detailed description, ⚠️only applies to aspects written in Java code
annotationProcessor("io.github.FlyJingFish.AndroidAop:android-aop-processor:2.3.0")
//⚠️Choose one of the above android-aop-ksp and android-aop-processor
}
- This library has built-in annotations for some functions defined using @AndroidAopPointCut
- When you use the five custom aspect annotations introduced here, it means that you must choose one from
android-aop-ksp
andandroid-aop-processor
as a required option - When you use the five custom aspect annotations introduced here, it means that you must choose one from
android-aop-ksp
andandroid-aop-processor
as a required option
Note
Tip: ksp or annotationProcessor can only scan the current module. Custom aspect codes are added to the module where they are located. But custom aspect codes are globally effective; required dependencies can be added only to public modules through the API.
4. Add the androidAopConfig configuration item in app’s build.gradle (this step is an optional configuration item)¶
- Related development configurations
plugins {
...
id 'android.aop'//It is best to put it on the last line
}
androidAopConfig {
// enabled is false, the aspect no longer works, the default is not written as true
enabled true
// include does not set all scans by default. After setting, only the code of the set package name will be scanned.
include 'Package name of your project', 'Package name of custom module', 'Package name of custom module'
// exclude is the package excluded during scanning
// Can exclude kotlin related and improve speed
exclude 'kotlin.jvm', 'kotlin.internal','kotlinx.coroutines.internal', 'kotlinx.coroutines.android'
// verifyLeafExtends Whether to turn on verification leaf inheritance, it is turned on by default. If type = MatchType.LEAF_EXTENDS of @AndroidAopMatchClassMethod is not set, it can be turned off.
verifyLeafExtends true
//Off by default, if enabled in Build or after packaging, the point cut information json file will be generated in app/build/tmp/cutInfo.json
cutInfoJson false
}
android {
...
}
plugins {
...
id("android.aop")//It is best to put it on the last line
}
androidAopConfig {
// enabled is false, the aspect no longer works, the default is not written as true
enabled = true
// include does not set all scans by default. After setting, only the code of the set package name will be scanned.
include("Package name of your project", "Package name of custom module", "Package name of custom module")
// exclude is the package excluded during scanning
// Can exclude kotlin related and improve speed
exclude("kotlin.jvm", "kotlin.internal","kotlinx.coroutines.internal", "kotlinx.coroutines.android")
// verifyLeafExtends Whether to turn on verification leaf inheritance, it is turned on by default. If type = MatchType.LEAF_EXTENDS of @AndroidAopMatchClassMethod is not set, it can be turned off.
verifyLeafExtends = true
//Off by default, if enabled in Build or after packaging, the point cut information json file will be generated in app/build/tmp/cutInfo.json
cutInfoJson = false
}
android {
...
}
Note
- Include and exclude support precise setting to a class
- Reasonable use of include and exclude can improve compilation speed. It is recommended to use include to set the relevant package name of your project (including app and custom module)
- If
LEAF_EXTENDS
is not set for@AndroidAopMatchClassMethod
and@AndroidAopCollectMethod
, settingverifyLeafExtends
to false can also speed up
Warning
After setting include and exclude, all aspects are only valid within the rules you set. Please remember your settings! In addition, since Android Studio may have cache after setting here, it is recommended to clean before continuing development
5. The code weaving method can be set during development (this step is an optional configuration item)¶
If you configure DebugMode in this step, please read the instructions in each line below carefully and do not copy them blindly, especially if you want to cut third-party jar packages.
The following configuration steps also apply to componentized scenarios Click here to view
For all sub-modules also rely on plug-ins, please follow the above step 1 method 1 to configure the project, then choose one of the following methods
-
Method 1 (recommended):
Follow the above Step 1 Method 1 Configuration Project and you are done. This method automatically applies debugMode to all Android modules
-
Method 2:
Please configure the project according to the above Step 1 Method 1 to configure the project, and then manually set the required sub-module module, for example:
Note
- This method can only apply debugMode to the modules you have added, and the related aspects in the modules that have not been added will not take effect
- If your module is a Java or Kotlin library, this method can only enable all Android libraries. You need to use method 2 to configure your module separately for it to take effect.
Add the following settings in gradle.properties
in the root directory
androidAop.debugMode=true //Set to true to use the current packaging method of your project, false to use the full packaging method, otherwise the default is false
Warning
Please note that when set to true, the compilation speed will be faster but some functions will be invalid. Only the aop code will be woven into the set module. The third-party jar package will not weave in the code, so please be careful to turn it off when building the official package. Configure this and clean the project
Add the following settings in gradle.properties
in the root directory
Note
1.If this option is not set, it will be true by default. Please note that when it is set to true, the release package will ignore the setting of androidAop.debugMode = true
and automatically use the full packaging method. When it is set to false, there will be no such effect
2.This feature is enabled by default, so the release package does not need to manually disable androidAop.debugMode
3. This feature is only valid for Android libraries, not for Java or Kotlin libraries
Add the following settings to gradle.properties
in the root directory (optional, you can configure this if you want to be the best)
androidAop.reflectInvokeMethod = true //Set to true to reflect the execution of the facet method, if not set, the default is false
androidAop.reflectInvokeMethod.variantOnlyDebug = true //Set to true to be effective only in debug, if not set, the default is false
androidAop.reflectInvokeMethod.static = true // Set to true to simulate non-reflective situations. If not set, the default value is true.
Note
androidAop.reflectInvokeMethod
is set to true to reflect the execution of the section method, which will speed up the packaging speed. If it is set to false, the secondary compilation speed is basically the same as the reflection speed.- Please note that when
androidAop.reflectInvokeMethod.variantOnlyDebug
is set to true, the release package will ignore the setting ofandroidAop.reflectInvokeMethod = true
and automatically not reflect. If it is set to false, there will be no such effect (default false if not written) androidAop.reflectInvokeMethod.static
is set to true to simulate the non-reflective situation and take into account the compilation speed of reflection. If it is not written, the default is true. If you want to use reflection, it is recommended to set this to true. Set it to false for pure reflectionandroidAop.reflectInvokeMethod.variantOnlyDebug
is only valid for Android libraries, not for Java or Kotlin libraries
Add the following settings to gradle.properties
in the root directory (optional)
androidAop.debugMode.buildConfig = true //If set to true, it means exporting a DebugModeBuildConfig.java file. If not set, the default value is true.
Note
Because some modules have only Kotlin code, debugMode cannot take effect. You can insert a Java code to make it effective by setting it to true. If you don't need it, you can set it to false, but you need to manually create a Java code.
This library has some built-in functional annotations for you to use directly.¶
Annotation name | Parameter description | Function description |
---|---|---|
@SingleClick | value = interval of quick clicks, default 1000ms | Click the annotation and add this annotation to make your method accessible only when clicked |
@DoubleClick | value = maximum time between two clicks, default 300ms | Double-click annotation, add this annotation to make your method enterable only when double-clicked |
@IOThread | ThreadType = thread type | Switch to the sub-thread operation. Adding this annotation can switch the code in your method to the sub-thread for execution |
@MainThread | No parameters | The operation of switching to the main thread. Adding this annotation can switch the code in your method to the main thread for execution |
@OnLifecycle* | value = Lifecycle.Event | Monitor life cycle operations. Adding this annotation allows the code in your method to be executed only during the corresponding life cycle |
@TryCatch | value = a flag you customized | Adding this annotation can wrap a layer of try catch code for your method |
@Permission* | value = String array of permissions | The operation of applying for permissions. Adding this annotation will enable your code to be executed only after obtaining permissions |
@Scheduled | initialDelay = delayed start time interval = interval repeatCount = number of repetitions isOnMainThread = whether to be the main thread id = unique identifier | Scheduled tasks, add this annotation to make your method Executed every once in a while, call AndroidAop.shutdownNow(id) or AndroidAop.shutdown(id) to stop |
@Delay | delay = delay time isOnMainThread = whether the main thread id = unique identifier | Delay task, add this annotation to delay the execution of your method for a period of time, call AndroidAop.shutdownNow(id) or AndroidAop .shutdown(id) can be canceled |
@CheckNetwork | tag = custom tag toastText = toast prompt when there is no network invokeListener = whether to take over the check network logic | Check whether the network is available, adding this annotation will allow your method to enter only when there is a network |
@CustomIntercept | value = a flag of a string array that you customized | Custom interception, used with AndroidAop.setOnCustomInterceptListener, is a panacea |
Note
The above functions are located in the android-aop-extra
library. For detailed instructions, please see the documentation
Custom Aspects¶
This introduction is a general outline.
- @AndroidAopPointCut is an aspect that annotates methods
- @AndroidAopMatchClassMethod is the aspect of matching class methods
- @AndroidAopReplaceClass is called by the replacement method
- @AndroidAopModifyExtendsClass is a modified inherited class
- @AndroidAopCollectMethod Is a collection inheritance class
@AndroidAopPointCut¶
It is used to make aspects in the form of annotations on the method. The above annotations are all made through this. Please see the wiki document for detailed usage
The following uses @CustomIntercept as an example to introduce how to use it.
-
Create annotations(You need to implement the BasePointCut interface, and fill in the annotations above for its generic type)
-
Create a class that annotates the aspect (needs to implement the BasePointCut interface, and fill in the above annotation with its generic type)
class CustomInterceptCut : BasePointCut<CustomIntercept> { override fun invoke( joinPoint: ProceedJoinPoint, annotation: CustomIntercept //annotation is the annotation you add to the method ): Any? { //Write your logic here // joinPoint.proceed() means to continue executing the logic of the point-cut method. If this method is not called, the code in the point-cut method will not be executed. // About ProceedJoinPoint, you can see the wiki document, click the link below for details return joinPoint.proceed() } }
About ProceedJoinPoint usage instructions, the same applies to ProceedJoinPoint below
-
use
Directly add the annotation you wrote to any method, for example, to onCustomIntercept(). When onCustomIntercept() is called, it will first enter the invoke method of CustomInterceptCut mentioned above.
@AndroidAopMatchClassMethod¶
It is used to match aspects of a certain class and its corresponding method.
The matching method supports accurate matching, click here to see detailed usage documentation on the wiki
-
Example 1
package com.flyjingfish.test_lib; public class TestMatch { public void test1(int value1,String value2){ } public String test2(int value1,String value2){ return value1+value2; } }
If TestMatch is the class to be matched, and you want to match the test2 method, the following is how to write the match:
package com.flyjingfish.test_lib.mycut; @AndroidAopMatchClassMethod( targetClassName = "com.flyjingfish.test_lib.TestMatch", methodName = ["test2"], type = MatchType.SELF ) class MatchTestMatchMethod : MatchClassMethod { override fun invoke(joinPoint: ProceedJoinPoint, methodName: String): Any? { Log.e("MatchTestMatchMethod","======"+methodName+",getParameterTypes="+joinPoint.getTargetMethod().getParameterTypes().length); //Write your logic here //If you don’t want to execute the original method logic, 👇 don’t call the following sentence return joinPoint.proceed() } }
You can see that the type set by AndroidAopMatchClassMethod above is MatchType.SELF, which means that it only matches the TestMatch class itself, regardless of its subclasses. - Example 2
If you want to Hook all onClicks of android.view.View.OnClickListener, to put it bluntly, you want to globally monitor all click events of OnClickListener. The code is as follows:
@AndroidAopMatchClassMethod( targetClassName = "android.view.View.OnClickListener", methodName = ["onClick"], type = MatchType.EXTENDS //type must be EXTENDS because you want to hook all classes that inherit OnClickListener ) class MatchOnClick : MatchClassMethod { // @SingleClick(5000) //Combined with @SingleClick, add multi-point prevention to all clicks, 6 is not 6 override fun invoke(joinPoint: ProceedJoinPoint, methodName: String): Any? { Log.e("MatchOnClick", "======invoke=====$methodName") return joinPoint.proceed() } }
You can see that the type set by AndroidAopMatchClassMethod above is MatchType.EXTENDS, which means matching all subclasses inherited from OnClickListener. For more inheritance methods, please refer to the Wiki document
Note: If the subclass does not have this method, the aspect will be invalid. In addition, do not match the same method multiple times in the same class, otherwise only one will take effect, Use overrideMethod to ignore this restriction Click here for details
@AndroidAopReplaceClass¶
It is used for replacement method calls
@AndroidAopReplaceClass and @AndroidAopReplaceMethod are used together
Detailed usage of replacement method call, click here to see detailed usage documentation in wiki
- Java writing method
@AndroidAopReplaceClass( "android.widget.Toast" ) public class ReplaceToast { @AndroidAopReplaceMethod( "android.widget.Toast makeText(android.content.Context, java.lang.CharSequence, int)" ) // Because the replaced method is static, the parameter type and order correspond to the replaced method one-to-one. public static Toast makeText(Context context, CharSequence text, int duration) { return Toast.makeText(context, "ReplaceToast-"+text, duration); } @AndroidAopReplaceMethod( "void setGravity(int , int , int )" ) // Because the replaced method is not a static method, the first parameter is the replaced class, and the subsequent parameters correspond to the replaced method one-to-one. public static void setGravity(Toast toast,int gravity, int xOffset, int yOffset) { toast.setGravity(Gravity.CENTER, xOffset, yOffset); } @AndroidAopReplaceMethod( "void show()" ) // Although the replaced method has no parameters, because it is not a static method, the first parameter is still the replaced class. public static void show(Toast toast) { toast.show(); } }
- Kotlin writing method
@AndroidAopModifyExtendsClass¶
It is an inherited class that modifies the target classDetailed usage
Usually, you replace one layer in the inheritance relationship of a certain class, then rewrite some functions, and add some logic code you want to the rewritten functions to monitor and rewrite the original logic.
As shown in the following example, you need to replace the inherited class of AppCompatImageView
with ReplaceImageView
-
Application scenario: non-invasively implement the function of monitoring large image loading
@AndroidAopModifyExtendsClass("androidx.appcompat.widget.AppCompatImageView") public class ReplaceImageView extends ImageView { public ReplaceImageView(@NonNull Context context) { super(context); } public ReplaceImageView(@NonNull Context context, @Nullable AttributeSet attrs) { super(context, attrs); } public ReplaceImageView(@NonNull Context context, @Nullable AttributeSet attrs, int defStyleAttr) { super(context, attrs, defStyleAttr); } @Override public void setImageDrawable(@Nullable Drawable drawable) { super.setImageDrawable(drawable); //做一些监测或者再次修改 } }
@AndroidAopCollectMethod¶
It is a aspects that collects inherited classes of a class detailed usage
It is extremely simple to use, the sample code has already explained
-
Example
object InitCollect { private val collects = mutableListOf<SubApplication>() private val collectClazz: MutableList<Class<out SubApplication>> = mutableListOf() @AndroidAopCollectMethod @JvmStatic fun collect(sub: SubApplication){ collects.add(sub) } @AndroidAopCollectMethod @JvmStatic fun collect2(sub:Class<out SubApplication>){ collectClazz.add(sub) } // Call this method directly. The collects collection contains data. fun init(application: Application){ for (collect in collects) { collect.onCreate(application) } } }
public class InitCollect2 { private static final List<SubApplication2> collects = new ArrayList<>(); private static final List<Class<? extends SubApplication2>> collectClazz = new ArrayList<>(); @AndroidAopCollectMethod public static void collect(SubApplication2 sub){ collects.add(sub); } @AndroidAopCollectMethod public static void collect3(Class<? extends SubApplication2> sub){ collectClazz.add(sub); } // Call this method directly. The collects collection contains data. public static void init(Application application){ Log.e("InitCollect2","----init----"); for (SubApplication2 collect : collects) { collect.onCreate(application); } } }