Closed W0lfbane closed 1 year ago
👋 @W0lfbane Issues is only for reporting a bug/feature request. For limited support, questions, and discussions, please join MobSF Slack channel Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.
If you can run the application from the VM/emulator, you should be able to run it with frida. We are launching the app with frida instrumentation https://github.com/MobSF/Mobile-Security-Framework-MobSF/blob/3c7c9afecd2ba6cd51dd860112331ce352a4b692/mobsf/DynamicAnalyzer/views/android/frida_core.py#L130
Couple of things can happen or to try out.
ENVIRONMENT
EXPLANATION OF THE ISSUE
This appears to only happen with split APKs, here is the issue:
First, after scanning the "base.apk" of a split apk package, I run the DAST scan against it. The DAST scanner only brings in base.apk and nothing else, so the application does not function normally. I am able to resolve this by running "adb install-multiple" to get the full app installed. Once this is done, I'm able to run activities and start the app normally, however when I click the button for instrumentation the app crashes immediately and I can find this in the logstream:
STEPS TO REPRODUCE THE ISSUE
LOG FILE
debug.log