Configuration

This guide is the full env-var reference for developers and operators who fork, brand, and self-publish the Fleetbase Navigator driver app. If your drivers will use the public Fleetbase Navigator app from the App Store / Google Play, see Navigator App Setup instead — that page covers installing the public app and connecting it to your instance via the console-generated deep link.

The Navigator source lives at github.com/fleetbase/navigator-app. It's a React Native 0.77 app, Expo-free, with Tamagui for styling and Fastlane for release automation.

To get the app running locally for the first time, see Quickstart. For colors, themes, and other visual branding, see Theming & Branding.

Prerequisites

Environment Variables

All configuration is driven by environment variables loaded via react-native-config. Start from .env.example and override per environment in .env.dev / .env.prod / a custom flavor file.

Core

Fleetbase Connection

These values are also baked into the deep link your console emits — so most drivers never touch them directly. They're the fallback when no deep link is provided.

Maps

Generate a key in the Google Cloud Console with Maps SDK for iOS, Maps SDK for Android, and Directions API enabled. Restrict the key to your bundle ID / package name in production.

Driver UI

Remove tabs your deployment doesn't need (e.g. drop DriverChatTab if you're not using built-in chat).

Android Signing

The Android release signing config in android/app/build.gradle reads these from the environment when present:

See Build & Release for keystore generation.

Minimal .env

For a first run pointing at the hosted Fleetbase backend:

APP_NAME=Acme Driver
APP_IDENTIFIER=com.acme.driver
APP_LINK_PREFIX=acmedriver
FLEETBASE_HOST=https://api.fleetbase.io
FLEETBASE_KEY=flb_live_xxxxxxxxxxxxxxxx
GOOGLE_MAPS_API_KEY=AIzaSyXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
DEFAULT_COORDINATES=1.369,103.8864

Connect to a Self-Hosted Fleetbase

Point FLEETBASE_HOST at your API domain and update the SocketCluster envs to match your realtime gateway:

FLEETBASE_HOST=https://api.acme.com
SOCKETCLUSTER_HOST=socket.acme.com
SOCKETCLUSTER_PORT=443
SOCKETCLUSTER_SECURE=true
SOCKETCLUSTER_PATH=/socketcluster/

The runtime config layer (src/contexts/ConfigContext.tsx) lets users override these at runtime by scanning a deep-link QR code from the console — so the env values function as defaults, not hard-codes.

Push Notifications

Navigator uses react-native-notifications for both FCM (Android) and APNS (iOS).

Background Geolocation

Navigator uses react-native-background-geolocation (Transistor Soft) for continuous driver tracking — including when the app is backgrounded or the device is locked. This is not the free react-native-geolocation-service package.

The wiring is already in place:

• Android: apply from: "${background_geolocation.projectDir}/app.gradle" at the top of android/app/build.gradle.
• iOS: Info.plist declares NSLocationAlwaysAndWhenInUseUsageDescription, NSLocationAlwaysUsageDescription, and the location background mode.
• App code: src/contexts/LocationContext.tsx configures and starts the plugin.

What you have to do per platform before a release build:

1. Purchase a license at docs.transistorsoft.com/purchase — one for iOS, one for Android.
2. Follow the setup guide to drop the license keys into:
   • Android: <meta-data android:name="com.transistorsoft.locationmanager.license" android:value="YOUR_LICENSE_KEY"/> in AndroidManifest.xml.
   • iOS: BackgroundGeolocation.license key in Info.plist.

Branding

For app icon, splash screen, theme colors, custom color overrides, named themes, and native display names, see Theming & Branding.

Localization

Default locale is set by DEFAULT_LOCALE. To add a new language:

1. Create a translations bundle and register it with react-native-i18n in the language context provider.
2. The user's runtime selection is persisted via react-native-mmkv-storage and survives reinstalls if the keychain entry persists.

The current locale negotiation falls back to the device locale when DEFAULT_LOCALE is unset.

Deep Linking

APP_LINK_PREFIX is the URL scheme registered with both platforms:

• iOS: declared in Info.plist under CFBundleURLTypes.
• Android: written as appLinkScheme into AndroidManifest.xml via manifestPlaceholders in android/app/build.gradle.

When the Fleetbase console emits an App Link for drivers to scan, the URL is shaped like:

<APP_LINK_PREFIX>://configure?host=https://api.acme.com&key=flb_live_xxx&socket_host=socket.acme.com&...

If you change APP_LINK_PREFIX, also change the matching value in your Fleetbase instance's fleetops.navigator.link_prefix config so the console emits a link the app will respond to.

Next

For running the app locally on iOS, Android, or web, see Quickstart. When you're ready to build release artifacts and ship to the stores, continue to Build & Release.