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

Unresolved strings since aapt2 #28

Open
FoelliX opened this issue Mar 23, 2018 · 0 comments
Open

Unresolved strings since aapt2 #28

FoelliX opened this issue Mar 23, 2018 · 0 comments

Comments

@FoelliX
Copy link

FoelliX commented Mar 23, 2018

Hello,

since gradle 3.0.0 aapt2 is used during compilation (https://developer.android.com/studio/build/gradle-plugin-3-0-0.html). The analyses of apps that are compiled without falling back to aapt (android.enableAapt2=false) seem to fail. Important parts such as action strings seem to be unresolved then.
The attached issue.zip contains two .apk files that clarify the issue. Both files represent the same app. The fallback was active/inactive while compiling Test.apk/Test2.apk respectively. For the latter one the action and category of all intent filters cannot be determined.
Any updates planed to fix this issue?

I hotfixed the issue by using the ApkParser to extract the manifest information: https://github.com/FoelliX/ic3
Please let me know if you want to pull the changes. Then i will come up with a pull request.

Regards,
FoelliX

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

1 participant