Issue:
My app.json has the correct bundle identifier set under the ios key:
"ios": {
"bundleIdentifier": "io.cirsiumlabs.drillshot"
}
After publishing through Replit’s App Store publishing flow, the bundle identifier is not showing up correctly in the resulting build details — either within Replit’s publish UI or in App Store Connect / TestFlight’s build metadata.
✅ Modified app.json with:{ "name": "DrillShot", "slug": "drillshot", "owner": "replit-private-07618964-7dc7-40dd-b99d-9f1e5fa879b0", "extra": { "eas": { "projectId": "80585504-fcd0-4419-ac81-f9374da63d1a" } }, "ios": { "appleTeamId": "8HN2MM9FSQ", "bundleIdentifier": "app.replit.drillshot", "infoPlist": { "ITSAppUsesNonExemptEncryption": false } }}
What I expected: The bundle identifier defined in app.json to carry through into the EAS build and be visible in the build details as io.cirsiumlabs.drillshot.
What I see: The build details either show a blank/missing bundle identifier or appear to reflect a previous value rather than the one currently in app.json.
Questions:
-
Does Replit’s Publish to App Store flow read the bundle identifier directly from
app.json, or does it need to be configured separately somewhere else in the publish settings? -
Is there a place within Replit’s publish flow to explicitly override or confirm the bundle identifier before the build is submitted?
Any guidance appreciated — the code-side config looks correct, so I suspect this is something specific to how the Replit publishing pipeline handles or surfaces the identifier.
Update (edit): Replit is silently replacing my slug and bundle identifier with auto-generated values before the EAS build runs.
- Is there a way to prevent Replit’s publish flow from overriding the bundle identifier I’ve already defined in
app.json? - Is there a setting in the publish UI to specify a custom bundle identifier instead of the auto-generated
app.replit.*one? - If Replit must manage the identifier, can it respect the one already present in
app.jsonrather than replacing it?