Skip to content

No apk is output with some combinations of vX-signing-enabled #5

@charlesastaylor

Description

@charlesastaylor

Hi,

With some combinations of setting --vX-signing-enabled to true/false no apk is showing up at the --out path (or anywhere) but no error is returned.

eg:

  • signapk.exe sign --ks .build_android/jai_debug.keystore --ks-pass pass:password --v1-signing-enabled false --v2-signing-enabled true --v3-signing-enabled true --out nogradle.apk .build_android/nogradle.unsigned.apk
  • signapk.exe sign --ks .build_android/jai_debug.keystore --ks-pass pass:password --v2-signing-enabled true --out nogradle.apk .build_android/nogradle.unsigned.apk
  • signapk.exe sign --ks .build_android/jai_debug.keystore --ks-pass pass:password --v4-signing-enabled true --out nogradle.apk .build_android/nogradle.unsigned.apk

The final one is less surprising because you say v4 is not supported, but in either case I would have expected an error if no apk was produced.

P.S. Thanks for this tool! It's great that someone has done this so I don't have to wonder whether there is any good reason for the default apksigner to be as slow as it is.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions