IssueTracker

This is also affecting me as well, but for a slightly (maybe?) different reason. I'm using Gradle Build Types to change my application ID before installation. However, the ndk-gdb script pulls the package name out of the manifest and tries to feed that into a run-as call, which is expecting the modified application ID. E.g. the package name from the manifest is com.company.game while the application Id is com.company.game.debug. Run-as fails and takes ndk-gdb with it.

I've modified the script to fit my needs, but this is essentially blocking adoption of the multiple build types feature via Gradle

Fix submitted:  https://android-review.googlesource.com/#/c/118441 thanks to Xiaolei Yu

TutuApp had "PACKAGE_NAME" issue in it's version 2.21.00 android version. The have recently released the latest TutuApp version https://appspopo.com/tutuapp/ with major bugs fixed so it won't any further restrict you from running the applications downloaded via Tutuapp.