Custom Bundle ID support for iOS app deployment

We’ve built a new iOS app using Base44 and have reached the deployment stage, but we’re currently blocked because the generated/exported app does not support using our existing/custom Apple Bundle ID.

For teams replacing or updating an existing iOS app, the Bundle ID is not optional — it needs to match the existing identifier in Apple Developer / App Store Connect. Without custom Bundle ID support, it becomes impossible to deploy the Base44-built app as an update to an existing App Store listing.

Use case:

• Existing iOS app already live in App Store Connect

• App has an established Bundle ID

• New version has been built in Base44

• Deployment is blocked because the Base44 Bundle ID does not match the existing iOS app Bundle ID

Requested feature:
Please allow users to define or override the iOS Bundle ID before build/export/deployment, ideally during the app configuration or publishing setup.

This would make Base44 much more viable for teams rebuilding or modernising existing apps, not just launching brand new ones.

At the moment, this is a critical blocker for us: the app is built, but cannot be deployed as an update because of the Bundle ID mismatch.