Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B buck
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 201
    • Issues 201
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • buck
  • Issues
  • #655
Closed
Open
Issue created Feb 14, 2016 by Administrator@rootContributor

Android build should fail with incorrect keystore alias

Created by: DanielGrech

Trying to build a project with a keystore as such:

Pertinent BUCK file contents:

/** 
    release.keystore.properties contents:

    key.alias=some_incorrect_alias
    key.store.password=password1
    key.alias.password=password1
*/

keystore(
    name = 'release',
    store = 'release.keystore',
    properties = 'release.keystore.properties',
    visibility = ['PUBLIC']
)

android_binary(
    name = 'myapp_release',
    manifest = ':release-manifest',
    keystore = '//keystore:release',
    package_type = 'release',
    deps = [
      ':main-lib'
    ]
)

The file release.keystore.properties has an incorrect alias listed. I expect that the buck build myapp_release command should fail if the alias is incorrect. Instead, it fails silently and the resulting APK is not signed.

Validated with the command:

jarsigner -verify -verbose -certs buck-out/gen/myapp_release.apk

  s = signature was verified 
  m = entry is listed in manifest
  k = at least one certificate was found in keystore
  i = at least one certificate was found in identity scope

no manifest.
jar is unsigned. (signatures missing or not parsable)
Assignee
Assign to
Time tracking