Can't find bundle URL when building iOS app with a duplicated and renamed Debug build scheme

[euclides-jr]

Minimal reproducible example

https://github.com/euclides-jr/expo-issue

What platform(s) does this occur on?

iOS

Did you reproduce this issue in a development build?

No (only happens in a standalone build)

Summary

App crashes on startup when running with:

expo run:ios --configuration StagingDebug

StagingDebug is just a duplicate of the Xcode Debug configuration with no other changes, duplicating the Release configuration works fine.

Steps to reproduce:

1. Create an expo project
2. Run expo prebuild
3. Open Xcode and duplicate the Debug configuration
4. Run expo run:ios --configuration StagingDebug
5. Exception: RCTFatalException: No bundle URL present.

Environment

expo-env-info 1.2.0 environment info:
System:
OS: macOS 13.6.2
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 21.6.1 - /opt/homebrew/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.19.0/bin/yarn
npm: 10.2.4 - /opt/homebrew/bin/npm
Managers:
CocoaPods: 1.14.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
IDEs:
Android Studio: 2023.2 AI-232.10227.8.2321.11479570
Xcode: 15.2/15C500b - /usr/bin/xcodebuild
npmPackages:
expo: ~51.0.7 => 51.0.7
react: 18.2.0 => 18.2.0
react-native: 0.74.1 => 0.74.1
npmGlobalPackages:
eas-cli: 9.0.6
expo-cli: 6.3.10
Expo Workflow: bare

Expo Doctor Diagnostics

Running 12 checks on your project...
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check for issues with metro config
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that native modules use compatible support package versions for installed Expo SDK
✔ Check that packages match versions required by installed Expo SDK
✔ Check native tooling versions

Didn't find any issues with the project!

[brentvatne]

hi there! if you run npx expo start first does that resolve the issue?

[euclides-jr]

@brentvatne It doesn't. it's very easy to reproduce.

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[brentvatne]

@euclides-jr - if you build the project in xcode, rather than with npx expo run:ios, and you have the dev server running before running the build - does that resolve it?

[euclides-jr]

Also tried that. No success. On 16 May 2024, at 23:29, Brent Vatne ***@***.***> wrote:  @euclides-jr<https://github.com/euclides-jr> - if you build the project in xcode, rather than with npx expo run:ios, and you have the dev server running before running the build - does that resolve it? — Reply to this email directly, view it on GitHub<#28910 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYJ3F2VTUQOVOEEEJFXF7LZCUQJ5AVCNFSM6AAAAABHZWI4D2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWGIZDCMBUHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[solonik1]

Hi there, any updates here? I have the same issue

[brentvatne]

@byCedric has investigated a bit, he might be able to share more context