Repository navigation
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work lista: buildBuilding flutter applications with the toolBuilding flutter applications with the toole: OS-version specificAffects only some versions of the relevant operating systemAffects only some versions of the relevant operating systemplatform-iosiOS applications specificallyiOS applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versionteam-iosOwned by iOS platform teamOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamTriaged by iOS platform team
Description
Steps to reproduce
1. Set this environment:
- Physical iPhone 14 Pro, iOS 17.3.1.1, Available storage 131.3 GB out of 256GB Capacity
- Xcode version 15.2 (15C500b)
- macOS Sonoma version 14.2.1 (23C71)
- Flutter Channel stable, 3.19.0
- Dart SDK version: 3.3.0 (stable)
2. Run the app on VScode or the Terminal
3. Error:
Xcode is taking longer than expected to start debugging the app. Ensure the project is opened in Xcode.
Error starting debug session in Xcode: Timed out waiting for CONFIGURATION_BUILD_DIR to update.
Could not run build/ios/iphoneos/Runner.app on 00008120-001A15C936A0C01E.
Try launching Xcode and selecting "Product > Run" to fix the problem:
open ios/Runner.xcworkspace
Error launching application on iPhone.
Expected results
The app should run on the iPhone with no issues.
Note:
- When I run the app from Xcode directly, the app runs.
- When I run the same app on a physical iPhone X, iOS 16.7.5, Available storage 114.19 GB out of 256GB Capacity it runs fine.
- When I build a new Flutter project and run the app, it runs just fine as well.
Actual results
Launching lib/main.dart on iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: xxxxxx
Xcode build done. 206.5s
You may be prompted to give access to control Xcode. Flutter uses Xcode to run your app. If access is not allowed, you can change this through your Settings > Privacy & Security > Automation.
Xcode is taking longer than expected to start debugging the app. Ensure the project is opened in Xcode.
Error starting debug session in Xcode: Timed out waiting for CONFIGURATION_BUILD_DIR to update.
Could not run build/ios/iphoneos/Runner.app on 00008120-001A15C936A0C01E.
Try launching Xcode and selecting "Product > Run" to fix the problem:
open ios/Runner.xcworkspace
Error launching application on iPhone.
Code sample
Code sample
[Paste your code here]Screenshots or Video
Logs
Logs
Launching lib/main.dart on iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: ZR3QGWZA6A
Xcode build done. 206.5s
You may be prompted to give access to control Xcode. Flutter uses Xcode to run your app. If access is not allowed, you can change this through your Settings > Privacy & Security > Automation.
Xcode is taking longer than expected to start debugging the app. Ensure the project is opened in Xcode.
Error starting debug session in Xcode: Timed out waiting for CONFIGURATION_BUILD_DIR to update.
Could not run build/ios/iphoneos/Runner.app on 00008120-001A15C936A0C01E.
Try launching Xcode and selecting "Product > Run" to fix the problem:
open ios/Runner.xcworkspace
Error launching application on iPhone.Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.0, on macOS 14.2.1 23C71 darwin-arm64, locale
en-KE)
[✓] Android toolchain - develop for Android devices (Android SDK version
32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.86.2)
[✓] Connected device (3 available)
[✓] Network resources
• No issues found!Reacted by Tomas Tisocco, cosminbodnariuc, Benji Farquhar, Colin Schmale, Sai Gokula Krishnan, Murshid Ahmed and igokom
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work lista: buildBuilding flutter applications with the toolBuilding flutter applications with the toole: OS-version specificAffects only some versions of the relevant operating systemAffects only some versions of the relevant operating systemplatform-iosiOS applications specificallyiOS applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versionteam-iosOwned by iOS platform teamOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamTriaged by iOS platform team
Type
Projects
- StatusShow more project fieldsDone



Activity
dam-ease commentedon Feb 27, 2024
Thanks for the report @ChristineWasike.
Please can you try launching/running the app from Xcode?
ChristineWasike commentedon Feb 27, 2024
Yes, I've tried launching from Xcode, it works without issues but soon after I try launching from VScode or the Terminal I get this issue. I need to launch from VScode or the Terminal for efficient development.
dam-ease commentedon Feb 28, 2024
Thanks for your response @ChristineWasike
Can you please try out the suggested solutions here https://stackoverflow.com/questions/62335493/could-not-run-build-ios-iphoneos-runner-app-on-try-launching-xcode-and-selecting to see if it works in your case?
ChristineWasike commentedon Feb 28, 2024
Hey there @dam-ease, thank you for your proposition, but I'm unable to locate the VPN & Device Management clickable section mentioned in the suggested solutions.

Here's a screenshot of what I see.
dam-ease commentedon Feb 29, 2024
Hello @ChristineWasike

Here, so when you run on your device the next time, it prompts you.
ChristineWasike commentedon Feb 29, 2024
Hey @dam-ease, I have followed the steps but still get the same issue
dam-ease commentedon Feb 29, 2024
Thanks for your response @ChristineWasike.
I'm unable to reproduce this on my end but this might be device or OS-specific per:
Also, seeing that it runs on Xcode but doesn't on other IDEs and terminal, I'll be labelling for more insights from the team.
Thank you
57 remaining items
[CP beta] Use LLDB as the default debugging method for iOS 17+ and Xc…
danagbemava-nc commentedon Aug 11, 2025
Hi @vashworth, I just tested this on master
3.33.0-1.0.pre-1343and beta3.35.0-0.2.prewith Xcode 26 beta 5. On beta, I was able to reproduce it with #144218 (comment), however, when testing on master, the same steps did not reproduce the issuevashworth commentedon Aug 11, 2025
Okay awesome, that's what I would expect. It hasn't made it to a published beta quite yet
danagbemava-nc commentedon Aug 12, 2025
@vashworth, is it safe to close this issue now?
Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (f…
[CP beta] Use LLDB as the default debugging method for iOS 17+ and Xc…
Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (f…
github-actions commentedon Sep 9, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (f…
Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (f…
Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (f…
Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (#…