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

Possibility of switching to bytecode/apk analyzing instead of source? #46

Closed
Dkhusainov opened this issue May 17, 2018 · 1 comment
Closed

Comments

@Dkhusainov
Copy link

Hello.

First of all, this is a great tool and I really like the concept, but it laks flexibility.

Right now it only works on source code. Which means It cannot detect Modules/Components from other libraries(because accessing their source code is very difficult). Or Providers/injectors generated in aar module. Also you have implement different rules for Kotlin.

Would you consider switching to analyzing apk directly? Here's the tool that does something simular, but it build graph of all the classes. https://github.com/alexzaitsev/apk-dependency-graph/issues

@dvdciri
Copy link
Owner

dvdciri commented Jun 2, 2018

Unfortunately there are no plans to support analization of the apk as this tool was intended to be use during development for refactoring or integration of the dependencies.

@dvdciri dvdciri closed this as completed Jun 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants