Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smali debugging support #99

Closed
niklashigi opened this issue Jan 30, 2021 · 1 comment
Closed

Smali debugging support #99

niklashigi opened this issue Jan 30, 2021 · 1 comment

Comments

@niklashigi
Copy link
Contributor

niklashigi commented Jan 30, 2021

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
  • 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.

Additional context
I created this issue after this discussion in the Telegram group.

@Surendrajat
Copy link
Member

Surendrajat commented Mar 6, 2022

@shroudedcode I found this https://github.com/Chaos1323/ASD and apart from some minor issues this works well for me.
image
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.

@Surendrajat Surendrajat reopened this Jul 31, 2022
@Surendrajat Surendrajat added debug discussion and removed feature New feature or request labels Mar 19, 2023
@Surendrajat Surendrajat closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants