-
Notifications
You must be signed in to change notification settings - Fork 538
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Xamarin.Android.Build.Tasks] EnvVar & File support for Signing APKs (#…
…3522) Fixes: #3513 Both `jarsigner` and `apksigner` provide a way to use both files and environment variables for the store and key passwords. For `jarsigner` you have to suffix the parameter switch with either `:env` or `:file` to use those options. For `apksigner` you have to prefix the value with either `:env`, `:file` or `:pass`. We currently only support raw passwords. This commit adds support for using both `env:` and `file:` for signing. When providing values for the MSBuild properties such as `$(AndroidSigningStorePass)` and `$(AndroidSigningKeyPass)` all they need to do is prefix the value with `env:` or `file:` to use the alternative parameters. /p:AndroidSigningKeyPass=env:MyPasswordEnvVar /p:AndroidSigningKeyPass=file:PathToPasswordFile This will stop passwords appearing in build logs etc.
- Loading branch information
1 parent
ed597fb
commit 04a4308
Showing
4 changed files
with
140 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters