Status Update
No update yet.
Comments
je...@google.com
ch...@google.com
an...@google.com
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.
Description
On Windows, it appears this path search has a bug where a final forward slash stays appended to the end of the parent directory's path. This gets concatenated with '/AndroidManifest.xml', which results in a path like C:/A//AndroidManifest.xml, which $(wildcard ...) does not glob correctly.
patching