Instrumenation Failure in some APKs

[Mann-Nariya]

The tool was failing in the instrumentation phase for a few APKs. The failures were mostly in the "Instrumentation" and the "Signing and Aligning" steps of the AndroLog.

Example APK hashes:

• 0A4B39A5B8CD09CCE0CD7C41C143C8385D220F1A390065150DB71849986666F2
• 00A1F4535540369D2DB6EE4AFEDD6C0D2C777405E62F74CED48198EC180544EE

Please take a look into this.
Thank you for your time.

[JordanSamhi]

Hi @Mann-Nariya ,

Thanks for reporting this issues.

Indeed with some apps, Androlog can fail due to Soot's limitations.
For instance for the app "00A1F4535540369D2DB6EE4AFEDD6C0D2C777405E62F74CED48198EC180544EE", the issue is related to this Soot's issue: secure-software-engineering/FlowDroid#61

Regarding the other APK, I was able to instrument it.

Could you report the command you used?

[Mann-Nariya]

Hi @Mann-Nariya ,

Thanks for reporting this issues.

Indeed with some apps, Androlog can fail due to Soot's limitations. For instance for the app "00A1F4535540369D2DB6EE4AFEDD6C0D2C777405E62F74CED48198EC180544EE", the issue is related to this Soot's issue: secure-software-engineering/FlowDroid#61

Regarding the other APK, I was able to instrument it.

Could you report the command you used?

java -jar AndroLog/target/androlog-0.1-jar-with-dependencies.jar -p <path_to_platforms_directory> -l MY_SUPER_LOG -o ./output/ -a 0A4B39A5B8CD09CCE0CD7C41C143C8385D220F1A390065150DB71849986666F2.apk -c -m -cp -s