For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
      • Applications
      • Application versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Create application versions
  • Edit application versions
  • Delete application versions
ReleasesApplications and app versions

Application versions

Was this page helpful?
Previous

Change history

Next
Built with
Applications and application version management are not available in LaunchDarkly's European Union (EU) instance
Users on the European Union (EU) instance of LaunchDarkly cannot use applications and application versions. This includes automatic application creation based on SDK usage, indicators of an application version's support status, and application version adoption metrics. However, flag usage metrics based on application version are supported. To learn more, read LaunchDarkly in the European Union (EU).

Overview

This topic explains how to create, edit, and delete application versions.

LaunchDarkly automatically creates application versions when a LaunchDarkly SDK evaluates a feature flag that contains application version information. You can edit and delete application versions from the Versions page of an existing application in the LaunchDarkly UI.

Not all SDKs support application versions

For a list of SDKs that support application versions, read the SDK configuration topic.

Create application versions

Similar to creating an application, LaunchDarkly automatically creates new application versions when it establishes a connection with a LaunchDarkly SDK that supports Application metadata configuration.

We strongly recommend also enabling automatic environment attribute collection as part of your SDK configuration. When this configuration is enabled, the SDK provides data on the mobile environment where an application is running, including the application version name and id. The SDK includes this data in the ld_application and ld_device contexts. To learn more, read Automatic environment attributes.

After the SDK has evaluated at least one feature flag using an ld_application context, you can create mobile targeting rules based on application and application version information in that context. To learn more, read Mobile targeting.

Add mobile targeting rules only after application version information is collected

You can only create a “Mobile” targeting rule, and target mobile apps and devices based on automatically collected application version information, if you have completed the following:

  • your feature flag has its “Available on mobile SDKs” toggle set to On. To learn more, read Creating new flags. LaunchDarkly accounts created after October 21, 2025 have this box checked by default.
  • you have already started to collect application information in the ld_application and ld_device context kinds. LaunchDarkly must receive these context kinds before it enables the option to create a mobile targeting rule. To learn more, read Automatic environment attributes.

Edit application versions

You can only edit an application version’s support status. Only application versions for “mobile” application kinds include a support status.

To edit an application version’s support status:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Applications.
  3. Find the application whose versions you want to edit and click its name. The application’s Versions page appears.
  4. In the list of versions, find the version you want to edit.
  5. Click the overflow menu and choose “Edit support status.”
  6. In the “Edit version support status” dialog, select the new Support status.
  7. Click Save.

You cannot modify an application version name or key.

Ensure your application key is unique per distributed application

Before you mark an application version as unsupported, make sure that the application key is unique for each separately distributed software binary.

For example, suppose you have a mobile app, “Example app,” that you distribute on both iOS and Android. Initially you create one application, with application key “example-app” and application version “1.0”. However, if you set the “1.0” application version to unsupported, then if you create a flag targeting rule based only on the supported status, the flag will target both iOS and Android. This may not be what you intend.

We recommend that you create different applications for each separately distributed software binary, and set the application key to a different value for each. To learn more, read Application metadata configuration.

You can also use the REST API: Update application version

Delete application versions

To delete an existing application version:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Applications.
  3. Find the application whose versions you want to delete and click its name. The application’s Versions page appears.
  4. In the list of versions, find the version you want to delete.
  5. Click the overflow menu and choose “Delete.”
  6. In the dialog, type the name or key of the version to confirm.
  7. Click Delete.

You can also use the REST API: Delete application version