I made the plugin to help others better understand the processes inside their application and made this article to show, that plugin development is not so hard as it can look. My way was to create my own communication standard between OkHttpProfiler Android Library (to produce the log messages to logcat from the application side), and the OkHttpProfiler Plugin for Android Studio to read these logs. All the rest depends on your imagination, how you can use it.

In my case, I receive all messages for a target PID. Here is the LogCatMessage class structure, it contains all the needed information. So you know that the device was connected from the IDeviceChangeListener, and you can add logcat listener to it. Going next, open the adle file, and modify it a little bit to set proper values for your new plugin: plugins Īnd methods: logCatListener.addListener(device, deviceListener) logCatListener.removeListener(device, deviceListener) Add the next line to the file: StudioCompilePath=PATH_TO_YOUR_ANDROID_STUDIOįor mac users, the PATH is /Applications/Android Studio.app/Contents (If you are using a different OS and you don’t know where is it located - just use Google)

That's why we should specify StudioCompilePath in the gradle.properties file of the project. Unfortunately, after 4.1, Android Studio and IntelliJ IDEA has some different realization of the same classes, so we MUST include libraries from the Android Studio if we are creating it for AS, and vice versa (see this thread). Now we have the project with the initial configuration for the plugin development, but we should set up it more.īefore Android Studio version 4.1, it was enough to use IntelliJ IDEA files for plugins development with ddmlib library usage.

Android studio intellij