Status Update
Comments
je...@google.com <je...@google.com>
ch...@google.com <ch...@google.com>
an...@google.com <an...@google.com> #2
Thank you very much for reporting this issue, Jack. Looks like the issue is caused by somewhat unnecessary and contrived logic in apksigner.bat, which is special-casing -J* parameters. Unfortunately, this logic doesn't handle whitespace containing parameters, even those which aren't -J*.
I've uploaded a tentative fixhttps://android-review.googlesource.com/#/c/394238/ for review. The patched apksigner.bat is attached. This fixes the issue on my Windows 10 box.
Jack, please test the fix in your environment and let us know whether it works for you too.
I've uploaded a tentative fix
Jack, please test the fix in your environment and let us know whether it works for you too.
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