{"_id":"590a04f8ed80861900cbc7bb","user":"55b2d5626862a10d00887af9","version":{"_id":"590a04f2ed80861900cbc737","project":"55b2d5baa74a380d00e290c4","__v":4,"createdAt":"2017-05-03T16:27:30.085Z","releaseDate":"2017-05-03T16:27:30.085Z","categories":["590a04f3ed80861900cbc738","590a04f3ed80861900cbc739","590a04f3ed80861900cbc73a","590a04f3ed80861900cbc73b","590a04f3ed80861900cbc73c","590a04f3ed80861900cbc73d","590a04f3ed80861900cbc73e","590a04f3ed80861900cbc73f","590a04f3ed80861900cbc740","590a04f3ed80861900cbc741","590a04f3ed80861900cbc742","590a04f3ed80861900cbc743","590a04f3ed80861900cbc744","590a04f3ed80861900cbc745","590a04f3ed80861900cbc746","590a04f3ed80861900cbc747","590a04f3ed80861900cbc748","590a04f3ed80861900cbc749","590a04f3ed80861900cbc74a","590a04f3ed80861900cbc74b","590a04f3ed80861900cbc74c","590a04f3ed80861900cbc74d","59124949de13f61900336a7a","5914b04e7c2c552d008b7104","5914b47242c6a22300b9dc20"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"7.0.0","version":"7"},"__v":0,"project":"55b2d5baa74a380d00e290c4","category":{"_id":"590a04f3ed80861900cbc743","project":"55b2d5baa74a380d00e290c4","__v":0,"version":"590a04f2ed80861900cbc737","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-11T22:26:36.700Z","from_sync":false,"order":13,"slug":"android-keystores","title":"Android Keystores"},"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-12T00:43:19.044Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Android Applications need to be code signed to be installable on devices. The signing identities are bundled in a Java KeyStore file - typically with the extension .keystore or .jks.\n\nDebug builds are typically code signed with an auto-generated KeyStore. Release builds - like the ones that eventually end up in the Play Store - will require to be code signed with a KeyStore that is associated with a Developer.\n\nTypically, your KeyStores will be checked into your source control repository. The repo's build.gradle file will reference these KeyStores for each product flavor and build type.\n\nBuddybuild will auto-generate KeyStores for you. So you'll typically never have to manage KeyStores yourself. But if you already have a KeyStore that identifies you or your development team, you can upload this to buddybuild. Every subsequent build of your app will pick up your uploaded KeyStores.\n\nTo upload your own KeyStores, follow the guide [here](doc:managing-your-keystores).","excerpt":"","slug":"keystore-basics","type":"basic","title":"KeyStore Basics"}
Android Applications need to be code signed to be installable on devices. The signing identities are bundled in a Java KeyStore file - typically with the extension .keystore or .jks. Debug builds are typically code signed with an auto-generated KeyStore. Release builds - like the ones that eventually end up in the Play Store - will require to be code signed with a KeyStore that is associated with a Developer. Typically, your KeyStores will be checked into your source control repository. The repo's build.gradle file will reference these KeyStores for each product flavor and build type. Buddybuild will auto-generate KeyStores for you. So you'll typically never have to manage KeyStores yourself. But if you already have a KeyStore that identifies you or your development team, you can upload this to buddybuild. Every subsequent build of your app will pick up your uploaded KeyStores. To upload your own KeyStores, follow the guide [here](doc:managing-your-keystores).