SuperCall | Android 6.0 - 10.0 第三方电话个人项目

Based on your builder error, the ExportAttribute is used to instruct the “Java code generator to export a Java method that becomes an Android Callable Wrapper (ACW)” and Dictionary is not a Java object (duh) and the Java code generator has no idea how to handle it.

One trick you can apply is to not use rebasing but to create your own class loaders during the loading of a proxy where the new class (and all of its synthetic classes) are loaded in a class loader with multiple parents:

OSGi class loader implementations typically use a ClassLoader.defineClass method which takes the expected class name as an argument: e.g. https://docs.oracle.com/en/java/javase/13/docs/api/java.base/java/lang/ClassLoader.html#defineClass(java.lang.String,byte%5B%5D,int,int). When supplying the expected class name, the class loader requires the class being defined to have its name match the expected class name. This is a nice sanity check.

So if the class loader is defining the class Foo, you cannot supply the byte array for a class with a different name such as a subclass.

You are not configuring Byte Buddy to retransform already loaded classes. You can do so by setting .with(RetransformationStrategy.RETRANSFORM) in the agent builder DSL.

If you can avoid retransformation, i.e. if you are only instrumenting application classes that are not loaded when the agent is executed, you can however skip this step. Rather, use string-based matchers and do not load the class. If you need a richer description, you can also use a TypePool.Default to let Byte Buddy parse class files without loading classes.

To see what Byte Buddy is doing, you can register a Listener.StreamWriting.toSystemOut() where all discovered classes are printed to the console, including any potential errors.

I assume that your retransformation is already failing. Did you try to add a listener to the retransformation process. What does Exception: java.lang.Exception thrown from the UncaughtExceptionHandler in thread "main" mean?

One thing that I noticed is that you do not adjust the module graph. The java.base module will not be able to see your interceptor which is most likely loaded in the unnamed module of the bootstrap loader. Did you try to add assureReadEdgeTo in your transformation where you point to your interceptor class?

Also, please note that Advice does allow you to skip or even repeat a method execution. Have a look at the javadoc of the enter or exit methods. Typically, when instrumenting bootstrap classes advice tends to be more reliable.

It seems you are using wrong annotations, or functionality.

I'd recommend check more simplest case. For example replace your implementation:

Byte code instrumentation only allows you to generate code that you could also write yourself. For your case, you would need to create a fairly intrusive instrumentation that I would not recommend:

1. Instrument your target method to accept a new parameter of type Class.
2. Instrument every caller to supply their type as an additional argument.

The better solution is surely what Holger suggested in the comments. Use StackWalker and if not available, fall back to sun.reflect.Reflection (which is present in all JVMs I know of).

Byte Buddy proxies methods by overriding them. If a method is not declared open in Kotlin, it is final in Java byte code. If you open your method, your logic should work again.

In case protected constructors are okay, then:

1. Change Sample() to protected Sample() to make Scenario 1 working: this makes no-args constructor accessible from the subclass produced by ByteBuddy.

2. Change Sample(String id) to protected Sample(String id) and then in getProxyObject(String id) change