[+] NO LAUNCHER FOUND, PLEASE SPECIFY A TARGET CLASS

[Himan6]

No description provided.

[tokenwizard]

I an confirm this behavior with multiple tested apks. I have updated to the latest apktool (2.3.1) and still get the same issue. If I run the kwetza script, the extracted AndroidManifest.xml looks like this:

If I just manually run apktool d <apkname.apk> then the resulting AndroidManifest.xml looks correct:

[tokenwizard]

I did a little more digging and in the kwetza.py script, if I remove some of the options form the apktool command line...
changing this:

to this:

(removing the -f and -r parameters) then the AndroidManifest.xml looks correct and kwetza will successfully locate the HOME Activity. I then get hung up at the readPayloads point:

It seems like kwetza is designed to NOT decode the resources when it extracts the apk, but then has trouble locating the Launcher because it is parsing the Manifest file looking for specific strings that do not exist in the encoded version of the file:

I'm certainly no coding expert, just pointing out what I found to hopefully help the cause!