Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Signature
Search
Keishin Yokomaku
May 22, 2015
Technology
1
400
Signature
The best practice to deal with keystore and signature in the project.
Keishin Yokomaku
May 22, 2015
Tweet
Share
More Decks by Keishin Yokomaku
See All by Keishin Yokomaku
Base64 in Android
keithyokoma
0
37
One screen, many BottomSheets
keithyokoma
0
430
LazyColumnのitemがViewPortの中で占める領域の割合を知りたい
keithyokoma
0
710
Build apps for Cars
keithyokoma
0
560
Save the state
keithyokoma
0
590
Either in Kotlin
keithyokoma
0
620
持続的なアプリ開発のためのDXを支える技術
keithyokoma
2
5.4k
Make the objects serializable with kotlinx.serialization
keithyokoma
0
5.3k
Kotlin で書く Gradle Custom Tasks
keithyokoma
0
570
Other Decks in Technology
See All in Technology
予期せぬコストの急増を障害のように扱う――「コスト版ポストモーテム」の導入とその後の改善
muziyoshiz
1
1.9k
Contract One Engineering Unit 紹介資料
sansan33
PRO
0
13k
Oracle Cloud Observability and Management Platform - OCI 運用監視サービス概要 -
oracle4engineer
PRO
2
14k
M&A 後の統合をどう進めるか ─ ナレッジワーク × Poetics が実践した組織とシステムの融合
kworkdev
PRO
1
450
外部キー制約の知っておいて欲しいこと - RDBMSを正しく使うために必要なこと / FOREIGN KEY Night
soudai
PRO
12
5.5k
SREのプラクティスを用いた3領域同時 マネジメントへの挑戦 〜SRE・情シス・セキュリティを統合した チーム運営術〜
coconala_engineer
2
650
What happened to RubyGems and what can we learn?
mikemcquaid
0
300
レガシー共有バッチ基盤への挑戦 - SREドリブンなリアーキテクチャリングの取り組み
tatsukoni
0
220
SREが向き合う大規模リアーキテクチャ 〜信頼性とアジリティの両立〜
zepprix
0
450
プロポーザルに込める段取り八分
shoheimitani
1
270
モダンUIでフルサーバーレスなAIエージェントをAmplifyとCDKでサクッとデプロイしよう
minorun365
4
200
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
10k
Featured
See All Featured
Crafting Experiences
bethany
1
49
How STYLIGHT went responsive
nonsquared
100
6k
Done Done
chrislema
186
16k
SERP Conf. Vienna - Web Accessibility: Optimizing for Inclusivity and SEO
sarafernandez
1
1.3k
[SF Ruby Conf 2025] Rails X
palkan
1
750
Digital Ethics as a Driver of Design Innovation
axbom
PRO
1
180
Unlocking the hidden potential of vector embeddings in international SEO
frankvandijk
0
170
Agile Actions for Facilitating Distributed Teams - ADO2019
mkilby
0
110
How to Build an AI Search Optimization Roadmap - Criteria and Steps to Take #SEOIRL
aleyda
1
1.9k
Principles of Awesome APIs and How to Build Them.
keavy
128
17k
Designing Powerful Visuals for Engaging Learning
tmiket
0
230
技術選定の審美眼(2025年版) / Understanding the Spiral of Technologies 2025 edition
twada
PRO
117
110k
Transcript
Signature @KeithYokoma - Drivemode, Inc. Shibuya.apk #1
KeithYokoma Keishin Yokomaku Drivemode, Inc. Android Engineer GitHub: https://github.com/KeithYokoma Qiita:
http://qiita.com/KeithYokoma e-Book: http://amzn.to/1mZNydv
None
Keystore • Containing “Key” and “Certification” • Every applications are
signed with keystore • The same applications are signed with the same keystore
• Valid until … • Store password: … • Key
alias: … • Key password: … • Owner informations … Keystore
debug.keystore release.keystore Signing app-debug.apk app-release.apk
The problem
The problem Where should we put the keystore?
None
• Possibility to lost keystore files • Who remembers password?
• Manual operation to share keystore files • Dull to copy them by hand Shared drive?
Shared drive? Yuck!
Put keystores in the repository
Repository • No chance to lost(we have a history!) •
Quick set up build env with just cloning • Note: Safe to share them in PRIVATE repo
None
Wait, how do we share keystore password?
Keystore password • Use `echo something_seed_value | md5` • Set
it as ENV value ‘export KSTOREPWD=…’ • Read ENV value from build.gradle
build.gradle android { signingConfigs { release { storePassword System.getenv("KSTOREPWD") keyPassword
System.getenv(“KEYPWD”) } } }
Looks Good To Me
Signature @KeithYokoma - Drivemode, Inc. Shibuya.apk #1