Open w31ha0 opened 7 years ago
Apktool's -d flag doesn't directly have anything to do with debugging in smalidea, although if it's what I think it is, it does modify the debugging information, so it could conceivably have some effect. But you should definitely be able to debug an application with smalidea without using apktool's -d option.
Are you seeing any error messages from the IDE when the breakpoints aren't working? There will be a little blinking red exclamation at the very bottom of the window, in the bottom status area.
I can get it to work now but it seems to throw a NoReadAccessException
Read access is allowed from event dispatch thread or inside read-action only (see com.intellij.openapi.application.Application.runReadAction())
Details: Current thread: Thread[ApplicationImpl pooled thread 3,4,main] 1463379633
; dispatch thread: false; isDispatchThread(): false
SystemEventQueueThread: Thread[AWT-EventQueue-0 2.3#AI-162.4069837 Studio, eap:false, os:Windows 7 6.1, java-version:JetBrains s.r.o 1.8.0_112-release-b06,6,main] 2122116129
Looks like it might be https://github.com/JesusFreke/smalidea-issues/issues/240
It seems to me that smalidea only works properly with Android studio when i use the -d debugging flag when disassembling the apk file using apktool.(e.g apktool d -d test.apk)(apktool < 2.1 since the -d debugging flag is deprecated from 2.1 onwards.) When i use a newer version of apktool instead (apktool 2.2.3), the breakpoints doesn't seem to trigger when I get the app to reach the relevant portion of smali code.
Is this a known issue?