Add TV update flow in Tentang and fix startup zone
This commit is contained in:
40
README.md
40
README.md
@@ -90,6 +90,46 @@ flutter analyze
|
||||
flutter test
|
||||
```
|
||||
|
||||
### Build Release APK
|
||||
|
||||
```bash
|
||||
./scripts/build_release_apk.sh
|
||||
```
|
||||
|
||||
Artifacts will be written to `dist/android/`:
|
||||
|
||||
- versioned APK: `jamshalat-masjid-screen-v<version>-build<code>.apk`
|
||||
- latest APK copy: `jamshalat-masjid-screen-latest.apk`
|
||||
- checksum file: `*.sha256`
|
||||
- update JSON template: `latest.json.example`
|
||||
|
||||
### Android Production Signing
|
||||
|
||||
Release APKs now require real signing config. Before building:
|
||||
|
||||
1. Copy [android/key.properties.example](/Users/dwindown/CascadeProjects/jamshalat-masjid-screen/android/key.properties.example) to `android/key.properties`
|
||||
2. Fill in your real keystore values
|
||||
3. Put the keystore file under `android/keystore/` or update `storeFile` accordingly
|
||||
|
||||
Example:
|
||||
|
||||
```properties
|
||||
storePassword=YOUR_STORE_PASSWORD
|
||||
keyPassword=YOUR_KEY_PASSWORD
|
||||
keyAlias=upload
|
||||
storeFile=keystore/upload-keystore.jks
|
||||
```
|
||||
|
||||
Notes:
|
||||
|
||||
- `android/key.properties`
|
||||
- `android/keystore/`
|
||||
- `*.jks`
|
||||
|
||||
are ignored by Git and must stay private.
|
||||
|
||||
The release build now fails fast if signing is not configured, so you cannot accidentally produce another debug-signed production APK.
|
||||
|
||||
## Current Stabilization Status
|
||||
|
||||
The app is in a workable development state, but not yet fully stabilized.
|
||||
|
||||
Reference in New Issue
Block a user