default.json at the root of the repository. Flags defined at the top level apply to all build flavors. Flavor-specific overrides (under the flavors key) take precedence over top-level defaults.
Values can be overridden by a
custom-reloaded.json file in your customization repository. See Customization for the full priority resolution order.Application identity
The display name of the application. Currently informational — the value baked into build configs may differ from what is shown in the launcher.
Maximum number of Wire accounts that can be signed in simultaneously on a single device.
When
false, the registration screen is hidden and users can only sign in to an existing account. Useful for enterprise deployments where self-registration is not permitted.Controls whether the SSO (Single Sign-On) login option is presented to users. Set to
false to hide the SSO entry point entirely.Feature flags
Enables the self-deleting messages feature, allowing users to send messages that automatically delete after a configurable timer.
Allows team members to generate shareable guest links for conversations so external participants can join without a Wire account.
When enabled, users can optionally protect guest room links with a password. Requires
enable_guest_room_link to be true.Enables the public channels feature, allowing conversations to be discoverable and joinable by users within the same team.
Controls availability of the Meetings feature. Enabled by default in the
dev flavor.Enables picture-in-picture mode for ongoing calls, allowing the call UI to float over other apps.
Enables the Android bubble UI for incoming messages and calls, showing floating conversation heads.
Enables controls for configuring message history retention options in channels. Enabled in the
dev flavor.Enables the conversation feeder, an alternative backend-driven approach to loading conversations. Enabled in
dev and internal flavors.Controls whether the conversation list uses paginated loading. When
false, all conversations are loaded at once.Enables emoji reactions during active calls.
Enables Collabora Online document editing integration within conversations.
When
true, only file types listed in file_restriction_list can be shared in conversations.Comma-separated list of permitted file extensions when
file_restriction_enabled is true. Defaults to a broad list of common formats.Forces calls to use a constant bitrate rather than variable bitrate. Can improve call stability on restricted networks.
Enables the cross-platform backup and restore feature, allowing conversation history to be transferred between devices.
Controls whether the app shows an in-app release notes screen after an update.
When
true, the app uses the new unified login flow (email or SSO code in a single field) for the default backend. When false, the classic welcome screen with separate login paths is shown. See ADR-0006.Security flags
When
true, all local data is wiped if the session cookie becomes invalid (e.g., after a forced logout from the backend). Recommended for high-security enterprise deployments.When
true, local data is wiped when the device is removed from the Wire team by an administrator.When
true, the app detects root access and wipes all local data to protect against extraction via elevated privileges.Reduces the minimum number of MLS key packages that must be available before the app uploads new ones. Intended for testing environments with constrained key package generation.
When
true, the app verifies the cryptographic signature of the build configuration before applying it. Disabled in the dev flavor to ease local development. Set to false only for non-production builds.List of Ed25519 public keys (Base64-encoded) used to verify the configuration signature when
enforce_configuration_signature is true.Default production keys:Certificate pinning configuration. Maps SHA-256 pin hashes to lists of hostname patterns.Only applies to production (
prod) flavor by default. Set to an empty object {} to disable pinning.Allows the app to reset the MLS (Messaging Layer Security) state for a conversation. Used as a recovery mechanism when MLS state becomes inconsistent.
When
true, applies a stricter filter when selecting MLS cipher suites, limiting compatibility to a narrower set of configurations. Set to false in the internal flavor.Enables read receipts for MLS-encrypted conversations.
Disables SSL certificate validation. Only enabled in the
dev flavor for connecting to local or self-signed backends. Never enable in production.Enterprise flags
Enables Enterprise Mobility Management (EMM) support via Android’s
RestrictionsManager. When enabled, IT administrators can push backend URL, SSO code, and other settings to managed devices via an MDM solution. See ADR-0008.When
true, the app lock (PIN/biometric screen) is enforced at the team level. Users cannot disable it.Number of seconds of inactivity before the app lock is triggered when
team_app_lock is true.Maximum number of results returned by remote user/team member searches.
Maximum number of team members fetched in a single slow sync operation. Limits memory pressure on large teams.
Developer flags
The following flags are configured per-flavor. They default tofalse at the global level and are enabled only in non-production flavors.
| Flag | dev | staging | beta | internal | fdroid | prod |
|---|---|---|---|---|---|---|
developer_features_enabled | true | true | true | true | false | false |
logging_enabled | true | true | true | true | false | false |
development_api_enabled | true | false | false | false | false | false |
ignore_ssl_certificates | true | — | — | — | — | — |
analytics_enabled | false | true | true | true | false | true |
Unlocks in-app developer options such as backend switching, debug menus, and experimental UI toggles. Enabled in all non-production flavors.
Enables verbose logging output. Disabled in
prod and fdroid builds to avoid leaking sensitive information into device logs.Enables use of development/unstable backend API endpoints. Only enabled in the
dev flavor.Controls visibility of the debug screen accessible from app settings. Note: this flag is set globally to
true by default; individual flavors may override it.Shows or hides the “Report a bug” menu item in the app settings screen.
Enables asynchronous log flushing for improved performance. Enabled in
dev, beta, and internal flavors.Enables the call quality feedback menu shown after calls end. Enabled in
dev, staging, beta, and internal flavors.Enables experimental Nomad profile support. Enabled in the
dev flavor.Enables database invalidation control mechanisms for testing purposes. Enabled in the
dev flavor, disabled in internal.Backend defaults
These URLs define the default backend the app connects to on first launch. Users can switch backends at runtime via a deep link (unless restricted by EMM configuration). See Backend configuration for details.Base URL for the Wire backend REST API.
URL for the Wire account management portal, used for password reset and account settings links.
WebSocket endpoint URL for real-time push messaging when
websocket_enabled_by_default is true.URL for the Wire team management web application.
URL of the client version blacklist endpoint. The app periodically fetches this to enforce minimum client versions.
Base URL for the Wire marketing/documentation website, used for help and support links.
Human-readable label for the default backend, displayed in developer/debug screens.
When
true, the app prefers persistent WebSocket connections for push notifications instead of FCM. Useful for environments without Google Play Services or on F-Droid builds.When
true, the app checks default_backend_url_blacklist and blocks usage if the current app version is listed.Push notifications
Firebase Cloud Messaging (FCM) sender ID for the production project. Override per-flavor for staging/dev environments.
Firebase application ID for the production project.
Google API key associated with the Firebase project for push notifications.
Firebase project ID. Staging and dev flavors use
wiregcmpushstaging.Enables exponential backoff retry logic for background notification sync failures.
Duration (in seconds) the sync connection stays alive after receiving a push notification when
background_notification_retry_enabled is true.Analytics
Enables anonymous usage analytics via Countly. Disabled by default in the
dev and fdroid flavors. Users can also opt out in app settings.| Flavor | Default |
|---|---|
prod | true |
staging | true |
beta | true |
internal | true |
dev | false |
fdroid | false |
Countly application key. Production builds use
4483f7a58ae3e70b3780319c4ccb5c88a037be49. Non-production flavors use a separate key.Base URL of the Countly analytics server.