Update From Old Version
Use this guide when you already have an eBroker app live on the Play Store and you are moving to a newer eBroker source code release. Skip this page for fresh setups.
1. Copy from the Old Build (Critical)
Before doing anything else, copy these two files from your previous project into the new one:
| Source (old project) | Destination (new project) |
|---|---|
android/app/keystore.jks | android/app/keystore.jks |
android/key.properties | android/key.properties |
If you lose
keystore.jks, you cannot publish updates to your existing Play Store listing using the same key. You can generate a newkeystore.jks, but you must then request a signing key reset through Google Play Console support and follow their verification process before publishing updates. Back it up to secure storage to avoid this.
2. Confirm Flutter Version
Check the Version Compatibility table and switch your Flutter SDK to match the eBroker version you are upgrading to.
For Flutter install / version-switching steps, see the Basic Setup ↗ guide.
3. Files to Edit (Master Reference)
These are every file you typically touch during an eBroker update. Each is covered in detail in its dedicated doc — this table is the single index.
| File | What changes | Doc |
|---|---|---|
lib/config/app_config.dart | App name, package name, host URL, deep link domain | Change App Name, Change Package Name, Connect Admin Panel, Setup Deep Link |
lib/theme.dart | Fallback theme colors | Theme Colors |
pubspec.yaml | Version name + version code | Change App Version |
android/app/src/main/AndroidManifest.xml | Maps API key, AdMob app ID, deep link schema | Map API Key, Setup AdMob, Setup Deep Link |
ios/Runner/AppDelegate.swift | Maps API key | Map API Key |
ios/Runner/Info.plist | AdMob GADApplicationIdentifier, deep link CFBundleURLSchemes | Setup AdMob, Setup Deep Link |
assets/app_icons/ | Launcher icon source | Change App Icon |
assets/svg/fallback/ | Splash, home, placeholder, login-bg fallbacks | Other Icons |
assets/languages/ | Language JSON files | Add Languages |
android/key.properties | Keystore path + passwords | Copy from old build (above) |
4. Pre-Flight Checklist
- Old
keystore.jksandkey.propertiesbacked up offline - Old bundle ID noted (must match new build, otherwise it becomes a different app on Play Store)
- Flutter SDK version matches Version Compatibility
- Firebase project for the old app is accessible (you will reuse it, not create a new one)
5. Next Step
Continue with the Setup Checklist on the Key Points page — start at step 3 (Change App Name).