Skip to main content
Skip to navigation

Correct an app's Bundle ID or package name

Correct a Bundle ID or package name mismatch without disrupting a released app.

AIAsk AIChatGPTClaude
Last reviewed: August 31, 2026

This article shows you how to correct an App Store Bundle ID or Google Play package name in RevenueCat. By the end, your build, store listing, and RevenueCat app configuration will use the same identifier.

Prerequisites​

  • Confirm the identifier in App Store Connect or Google Play Console.
  • Confirm the identifier used by the app build.

1. Determine whether this is a correction or a new app​

Edit an existing RevenueCat app configuration only when its identifier is wrong and you need it to match the same store app.

If the same store app moved to another developer account, keep its existing identifier and RevenueCat app configuration. Update its store credentials instead.

Don't edit a production app configuration to point it to a different store app. Bundle IDs and package names identify store apps permanently after you upload a build or app artifact. A different identifier represents a different store app and requires a new RevenueCat app configuration.

❗️Keep released app configurations intact

Changing a production configuration to a different store identity can prevent existing app versions from loading Products or validating purchases. Keep the old configuration while released versions still use it.

2. Correct the identifier in RevenueCat​

  1. Open your project in the RevenueCat dashboard.
  2. Select Apps, then select the affected app.
  3. Update App Bundle ID for an App Store app or Package name for a Google Play app.
  4. Enter the identifier exactly as it appears in the store. Package names and Bundle IDs are case-sensitive. For Google Play, type the package name manually using standard periods (.). Pasting it can introduce visually identical Unicode dot characters that Google treats as a different package name.
  5. Save the app settings.

The app configuration keeps its existing public SDK key. Correcting the identifier doesn't update App Store Connect, Google Play Console, or your app binary.

After saving the correction:

  1. Confirm your build uses the same Bundle ID or package name.
  2. Run the store credential validation in the RevenueCat app settings.
  3. Confirm the correct store Products are present in the Product catalog.
  4. Confirm those Products are attached to the intended Entitlements and Offering Packages.
  5. Verify that your app uses the public SDK key shown for this RevenueCat app configuration.
  6. Make a Sandbox purchase and test restoring purchases.

For Google Play package-name errors, follow the Google Play credential troubleshooting checklist.

Use a new app configuration for a new store identity​

If you created a new App Store or Google Play listing with a different identifier:

  1. Add a new app configuration to the intended RevenueCat project.
  2. Configure and validate its store credentials.
  3. Import or recreate its Products.
  4. Attach the Products to the intended Entitlements and Offering Packages.
  5. Configure server notifications for the new store app.
  6. Update the new app build to use the new configuration's public SDK key.
  7. Test purchases, restores, and Entitlement access before release.

Keep the old RevenueCat app configuration for installed versions of the old store app and for historical reporting.

Limitations​

Editing an identifier doesn't move an app between RevenueCat projects or transfer its store ownership. See Merging RevenueCat Projects or Update RevenueCat after a developer-account transfer for those workflows.

Next steps​

Was this page helpful?