Android Release Build (Google Play)
Generate your production upload keystore, configure release signing, and produce the Android App Bundle (.aab) for Google Play.
The BookMyStay Customer application comes pre-configured with Gradle release signing logic. You only need to generate your private upload keystore and add a local key.properties file.
1. Generate the private keystore
In terminal, navigate to customer/android and execute keytool:
cd customer/android
keytool -genkey -v -keystore upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload
Enter a secure password, fill out the basic organization prompts (or press Enter), and confirm with yes.
2. Create key.properties
Create a file named key.properties in customer/android/:
storePassword=your-keystore-password
keyPassword=your-keystore-password
keyAlias=upload
storeFile=upload-keystore.jks
3. Set the version number
Open customer/pubspec.yaml and set your version string: version: 1.0.0+1. The build number after + must increase for every release submitted to the Play Console (e.g. 1.0.1+2).
4. Compile the Android App Bundle (.aab)
cd ..
flutter clean
flutter pub get
flutter build appbundle --release
| Artifact Type | Build Command | Output File Location | Intended Use |
|---|---|---|---|
| AAB (App Bundle) | flutter build appbundle --release |
customer/build/app/outputs/bundle/release/app-release.aab |
Google Play Console upload & production distribution |
| APK (Standalone) | flutter build apk --release |
customer/build/app/outputs/flutter-apk/app-release.apk |
Direct sideload testing on physical Android devices |
Securely back up your upload-keystore.jks
Store your upload-keystore.jks and password in a secure password vault. If you lose this file, Google Play will reject future updates until you file an upload key reset request with Google Play Developer support.
After your initial upload to Google Play Console, copy the App Signing SHA-1 and SHA-256 fingerprints into your Firebase Android app settings: see SHA Keys Guide.