Skip to main content

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.jksandroid/app/keystore.jks
android/key.propertiesandroid/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 new keystore.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.

FileWhat changesDoc
lib/settings.dartApp name, package name, host URL, deep link domainChange App Name, Change Package Name, Connect Admin Panel, Setup Deep Link
lib/theme.dartFallback theme colorsTheme Colors
pubspec.yamlVersion name + version codeChange App Version
android/app/src/main/AndroidManifest.xmlMaps API key, AdMob app ID, deep link schemaMap API Key, Setup AdMob, Setup Deep Link
ios/Runner/AppDelegate.swiftMaps API keyMap API Key
ios/Runner/Info.plistAdMob GADApplicationIdentifier, deep link CFBundleURLSchemesSetup AdMob, Setup Deep Link
assets/app_icons/Launcher icon sourceChange App Icon
assets/svg/fallback/Splash, home, placeholder, login-bg fallbacksOther Icons
assets/languages/Language JSON filesAdd Languages
android/key.propertiesKeystore path + passwordsCopy from old build (above)

4. Pre-Flight Checklist

  • Old keystore.jks and key.properties backed 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).