You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Being able to look at and modify an app's Smali code is often enough to get a general understanding of its internals and make small changes, but sometimes it can be helpful to set a few breakpoints and inspect behavior at runtime. This is already possible with the smalidea plugin for IntelliJ IDEA, but the process is kind of tedious. It requires you to:
(Obviously) Install the plugin
Realize that it doesn't work in Android Studio for some reason
Waste a lot of time wondering why you can't set any breakpoints inside Smali files
Open the "Android Device Monitor" application buried within the Android SDK folder
Switch to Java 8 because it doesn't work with newer Java versions
See which port is listed next to the app you want to debug
Create a new debug configuration inside IntelliJ IDEA and enter the port there
Finally start the debugging session
To be fair, some of the things above only have to be done once, but even without them the process isn't exactly smooth.
Describe the solution you'd like
It would be great if APKLab allowed users to quickly start a Smali debugging session by automatically finding the right debugging port based on the package name (this could be helpful), connecting to it, and launching a VS Code debugging session.
The bulk of this feature should probably live in the Smalise extension (which has its own issue for this), but APKLab could provide a nice "launcher" around it which ensures that you've built the APK with the --debug flag and automatically figures out the port.
@shroudedcode I found this https://github.com/Chaos1323/ASD and apart from some minor issues this works well for me.
So now I'm thinking of just creating a launch.json during decompilation and be done with it.
Let me know what you think of it.
Is your feature request related to a problem? Please describe.
Being able to look at and modify an app's Smali code is often enough to get a general understanding of its internals and make small changes, but sometimes it can be helpful to set a few breakpoints and inspect behavior at runtime. This is already possible with the smalidea plugin for IntelliJ IDEA, but the process is kind of tedious. It requires you to:
*.smali
from "Smali" to "smali files" in the settingsTo be fair, some of the things above only have to be done once, but even without them the process isn't exactly smooth.
Describe the solution you'd like
It would be great if APKLab allowed users to quickly start a Smali debugging session by automatically finding the right debugging port based on the package name (this could be helpful), connecting to it, and launching a VS Code debugging session.
The bulk of this feature should probably live in the Smalise extension (which has its own issue for this), but APKLab could provide a nice "launcher" around it which ensures that you've built the APK with the
--debug
flag and automatically figures out the port.Additional context
I created this issue after this discussion in the Telegram group.
The text was updated successfully, but these errors were encountered: