Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ #173443

vashworth · 2025-08-07T22:52:07Z

This PR introduces a new feature flag called lldb-debugging, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of devicectl and lldb to install, launch, and debug the app.

If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation.

This PR also adds analytics to track what deployment method is used and if it's successful.

Part 2 and 3 of #173416.

Fixes #144218. Fixes #133465.

Pre-launch Checklist

I read the Contributor Guide and followed the process outlined there for submitting PRs.
I read the Tree Hygiene wiki page, which explains my responsibilities.
I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
I signed the CLA.
I listed at least one issue that this PR fixes in the description above.
I updated/added relevant documentation (doc comments with ///).
I added new tests to check the change I am making, or this PR is test-exempt.
I followed the breaking change policy and added Data Driven Fixes where supported.
All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

gemini-code-assist

Code Review

This pull request introduces LLDB as the default debugging method for iOS 17+ devices when using Xcode 16+. It adds a new feature flag, lldbDebugging, which is enabled by default. The implementation includes a fallback to the existing Xcode debugging method if LLDB fails. Extensive analytics have been added to track the different iOS deployment methods. The changes also include significant refactoring of the iOS device launching logic for better modularity and the addition of a new devicelab test to cover the Xcode debugging path. Overall, this is a solid improvement to the iOS debugging experience.

packages/flutter_tools/lib/src/ios/devices.dart

vashworth · 2025-08-08T00:12:43Z

packages/flutter_tools/lib/src/device.dart

-      if (debuggingEnabled && !isCoreDevice) ...<String>[
-        '--enable-checked-mode',
-        '--verify-entry-points',
-      ],


This was specific to debugging through Xcode, so I moved it here:

flutter/packages/flutter_tools/lib/src/ios/devices.dart

Lines 1085 to 1090 in b02a1f4

// Core Devices (iOS 17 devices) are debugged through Xcode so don't

// include these flags, which are used to check if the app was launched

// via Flutter CLI and `ios-deploy`.

final List<String> filteredLaunchArguments = launchArguments

.where((String arg) => arg != '--enable-checked-mode' && arg != '--verify-entry-points')

.toList();

vashworth · 2025-08-08T03:02:47Z

packages/flutter_tools/lib/src/ios/devices.dart

      );
+      final bool launchSuccess = launchResult != null && launchResult.outcome == 'success';

-      return launchSuccess;


The diff here sucks due to spacing.

The changes made here:

Updated returns to return a bool and a IOSDeploymentMethod

If LLDB feature flag is enabled and Xcode 26+, use LLDB debugging

Updated timeout warning message for Xcode debugging

Filter out some arguments when Xcode debugging

Here's the function before:

flutter/packages/flutter_tools/lib/src/ios/devices.dart

Lines 894 to 1003 in 796c62b

Future<bool> _startAppOnCoreDevice({

required DebuggingOptions debuggingOptions,

required IOSApp package,

required List<String> launchArguments,

required String? mainPath,

required ShutdownHooks shutdownHooks,

@visibleForTesting Duration? discoveryTimeout,

}) async {

if (!debuggingOptions.debuggingEnabled) {

// Release mode

// Install app to device

final bool installSuccess = await _coreDeviceControl.installApp(

deviceId: id,

bundlePath: package.deviceBundlePath,

);

if (!installSuccess) {

return installSuccess;

}

// Launch app to device

final bool launchSuccess = await _coreDeviceControl.launchApp(

deviceId: id,

bundleId: package.id,

launchArguments: launchArguments,

);

return launchSuccess;

} else {

_logger.printStatus(

'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.',

);

final launchTimeout = isWirelesslyConnected ? 45 : 30;

final timer = Timer(discoveryTimeout ?? Duration(seconds: launchTimeout), () {

_logger.printError(

'Xcode is taking longer than expected to start debugging the app. '

'Ensure the project is opened in Xcode.',

);

});

XcodeDebugProject debugProject;

final FlutterProject flutterProject = FlutterProject.current();

if (package is PrebuiltIOSApp) {

debugProject = await _xcodeDebug.createXcodeProjectWithCustomBundle(

package.deviceBundlePath,

templateRenderer: globals.templateRenderer,

verboseLogging: _logger.isVerbose,

);

} else if (package is BuildableIOSApp) {

// Before installing/launching/debugging with Xcode, update the build

// settings to use a custom configuration build directory so Xcode

// knows where to find the app bundle to launch.

final Directory bundle = _fileSystem.directory(package.deviceBundlePath);

await updateGeneratedXcodeProperties(

project: flutterProject,

buildInfo: debuggingOptions.buildInfo,

targetOverride: mainPath,

configurationBuildDir: bundle.parent.absolute.path,

);

final IosProject project = package.project;

final XcodeProjectInfo? projectInfo = await project.projectInfo();

if (projectInfo == null) {

globals.printError('Xcode project not found.');

return false;

}

if (project.xcodeWorkspace == null) {

globals.printError('Unable to get Xcode workspace.');

return false;

}

final String? scheme = projectInfo.schemeFor(debuggingOptions.buildInfo);

if (scheme == null) {

projectInfo.reportFlavorNotFoundAndExit();

}

_xcodeDebug.ensureXcodeDebuggerLaunchAction(project.xcodeProjectSchemeFile(scheme: scheme));

debugProject = XcodeDebugProject(

scheme: scheme,

xcodeProject: project.xcodeProject,

xcodeWorkspace: project.xcodeWorkspace!,

hostAppProjectName: project.hostAppProjectName,

expectedConfigurationBuildDir: bundle.parent.absolute.path,

verboseLogging: _logger.isVerbose,

);

} else {

// This should not happen. Currently, only PrebuiltIOSApp and

// BuildableIOSApp extend from IOSApp.

_logger.printError('IOSApp type ${package.runtimeType} is not recognized.');

return false;

}

final bool debugSuccess = await _xcodeDebug.debugApp(

project: debugProject,

deviceId: id,

launchArguments: launchArguments,

);

timer.cancel();

// Kill Xcode on shutdown when running from CI

if (debuggingOptions.usingCISystem) {

shutdownHooks.addShutdownHook(() => _xcodeDebug.exit(force: true));

}

return debugSuccess;

}

}

and after:

flutter/packages/flutter_tools/lib/src/ios/devices.dart

Lines 955 to 1106 in 261be4b

Future<(bool, IOSDeploymentMethod)> _startAppOnCoreDevice({

required DebuggingOptions debuggingOptions,

required IOSApp package,

required List<String> launchArguments,

required String? mainPath,

required ShutdownHooks shutdownHooks,

@visibleForTesting Duration? discoveryTimeout,

}) async {

if (!debuggingOptions.debuggingEnabled) {

// Release mode

// Install app to device

final bool installSuccess = await _coreDeviceControl.installApp(

deviceId: id,

bundlePath: package.deviceBundlePath,

);

if (!installSuccess) {

return (installSuccess, IOSDeploymentMethod.coreDeviceWithoutDebugger);

}

// Launch app to device

final IOSCoreDeviceLaunchResult? launchResult = await _coreDeviceControl.launchApp(

deviceId: id,

bundleId: package.id,

launchArguments: launchArguments,

);

final bool launchSuccess = launchResult != null && launchResult.outcome == 'success';

return (launchSuccess, IOSDeploymentMethod.coreDeviceWithoutDebugger);

}

IOSDeploymentMethod? deploymentMethod;

// Xcode 16 introduced a way to start and attach to a debugserver through LLDB.

// However, it doesn't work reliably until Xcode 26.

// Use LLDB if Xcode version is greater than 26 and the feature is enabled.

final Version? xcodeVersion = globals.xcode?.currentVersion;

final bool lldbFeatureEnabled = featureFlags.isLLDBDebuggingEnabled;

if (xcodeVersion != null && xcodeVersion.major >= 26 && lldbFeatureEnabled) {

final bool launchSuccess = await _coreDeviceLauncher.launchAppWithLLDBDebugger(

deviceId: id,

bundlePath: package.deviceBundlePath,

bundleId: package.id,

launchArguments: launchArguments,

);

// If it succeeds to launch with LLDB, return, otherwise continue on to

// try launching with Xcode.

if (launchSuccess) {

return (launchSuccess, IOSDeploymentMethod.coreDeviceWithLLDB);

} else {

deploymentMethod = IOSDeploymentMethod.coreDeviceWithXcodeFallback;

_analytics.send(

Event.appleUsageEvent(

workflow: 'ios-physical-deployment',

parameter: IOSDeploymentMethod.coreDeviceWithLLDB.name,

result: 'launch failed',

),

);

}

}

deploymentMethod ??= IOSDeploymentMethod.coreDeviceWithXcode;

// If LLDB is not available or fails, fallback to using Xcode.

_logger.printStatus(

'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.',

);

final launchTimeout = isWirelesslyConnected ? 45 : 30;

final timer = Timer(discoveryTimeout ?? Duration(seconds: launchTimeout), () {

_logger.printError(

'Xcode is taking longer than expected to start debugging the app. '

'If the issue persists, try closing Xcode and re-running your Flutter command.',

);

});

XcodeDebugProject debugProject;

final FlutterProject flutterProject = FlutterProject.current();

if (package is PrebuiltIOSApp) {

debugProject = await _xcodeDebug.createXcodeProjectWithCustomBundle(

package.deviceBundlePath,

templateRenderer: globals.templateRenderer,

verboseLogging: _logger.isVerbose,

);

} else if (package is BuildableIOSApp) {

// Before installing/launching/debugging with Xcode, update the build

// settings to use a custom configuration build directory so Xcode

// knows where to find the app bundle to launch.

final Directory bundle = _fileSystem.directory(package.deviceBundlePath);

await updateGeneratedXcodeProperties(

project: flutterProject,

buildInfo: debuggingOptions.buildInfo,

targetOverride: mainPath,

configurationBuildDir: bundle.parent.absolute.path,

);

final IosProject project = package.project;

final XcodeProjectInfo? projectInfo = await project.projectInfo();

if (projectInfo == null) {

globals.printError('Xcode project not found.');

return (false, deploymentMethod);

}

if (project.xcodeWorkspace == null) {

globals.printError('Unable to get Xcode workspace.');

return (false, deploymentMethod);

}

final String? scheme = projectInfo.schemeFor(debuggingOptions.buildInfo);

if (scheme == null) {

projectInfo.reportFlavorNotFoundAndExit();

}

_xcodeDebug.ensureXcodeDebuggerLaunchAction(project.xcodeProjectSchemeFile(scheme: scheme));

debugProject = XcodeDebugProject(

scheme: scheme,

xcodeProject: project.xcodeProject,

xcodeWorkspace: project.xcodeWorkspace!,

hostAppProjectName: project.hostAppProjectName,

expectedConfigurationBuildDir: bundle.parent.absolute.path,

verboseLogging: _logger.isVerbose,

);

} else {

// This should not happen. Currently, only PrebuiltIOSApp and

// BuildableIOSApp extend from IOSApp.

_logger.printError('IOSApp type ${package.runtimeType} is not recognized.');

return (false, deploymentMethod);

}

// Core Devices (iOS 17 devices) are debugged through Xcode so don't

// include these flags, which are used to check if the app was launched

// via Flutter CLI and `ios-deploy`.

final List<String> filteredLaunchArguments = launchArguments

.where((String arg) => arg != '--enable-checked-mode' && arg != '--verify-entry-points')

.toList();

final bool debugSuccess = await _xcodeDebug.debugApp(

project: debugProject,

deviceId: id,

launchArguments: filteredLaunchArguments,

);

timer.cancel();

// Kill Xcode on shutdown when running from CI

if (debuggingOptions.usingCISystem) {

shutdownHooks.addShutdownHook(() => _xcodeDebug.exit(force: true));

}

return (debugSuccess, deploymentMethod);

}

bkonyi

LGTM!

bkonyi · 2025-08-08T14:18:10Z

packages/flutter_tools/lib/src/ios/devices.dart

+      // try launching with Xcode.
+      if (launchSuccess) {
+        return (launchSuccess, IOSDeploymentMethod.coreDeviceWithLLDB);
+      } else {


Ubernit: is this else necessary?

…ode 26+ (flutter/flutter#173443)

flutteractionsbot · 2025-08-08T18:08:36Z

Failed to create CP due to merge conflicts.
You will need to create the PR manually. See the cherrypick wiki for more info.

…lutter#173443) This PR introduces a new feature flag called `lldb-debugging`, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of `devicectl` and `lldb` to install, launch, and debug the app. If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation. This PR also adds analytics to track what deployment method is used and if it's successful. Part 2 and 3 of flutter#173416. Fixes flutter#144218. Fixes flutter#133465. - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

flutter/flutter@92a6bfb...3821790 2025-08-08 [email protected] Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ (flutter/flutter#173443) 2025-08-08 [email protected] Roll Fuchsia Linux SDK from i4vsuEGyP8Xeb5tiy... to HclTm0V8hgSpfqmtG... (flutter/flutter#173462) 2025-08-08 [email protected] Support launching a HTTPS URL (flutter/flutter#164720) 2025-08-08 [email protected] Roll Dart SDK from c48772a79e1f to 4b7b565eb468 (1 revision) (flutter/flutter#173454) 2025-08-08 [email protected] Roll Dart SDK from ba58b96a80d7 to c48772a79e1f (3 revisions) (flutter/flutter#173451) 2025-08-07 [email protected] Web dev proxy (flutter/flutter#172175) 2025-08-07 [email protected] Roll ICU from b929596baebf to 1b2e3e8a421e (7 revisions) (flutter/flutter#173436) 2025-08-07 [email protected] [A11y] TextField prefix icon and suffix icon create a sibling node' (flutter/flutter#173312) 2025-08-07 [email protected] [Android templates] Remove jetifier usage (flutter/flutter#173431) 2025-08-07 [email protected] Remove a couple of asserts from display_list_unittest (flutter/flutter#173381) 2025-08-07 [email protected] Fix ScaffoldGeometry null scale with noAnimation FAB (flutter/flutter#172914) 2025-08-07 [email protected] Prepare for iOS debugging with lldb and devicectl (flutter/flutter#173417) 2025-08-07 [email protected] Fix `ReorderableList` proxy animation for partial drag-back (flutter/flutter#172380) 2025-08-07 [email protected] [ios26]Do not report error for Info.plist key not found (flutter/flutter#172913) 2025-08-07 [email protected] Manual roll to 3.10.0-75.1.beta (flutter/flutter#173423) 2025-08-07 [email protected] [web] add --static-assets-url argument to build web (flutter/flutter#171638) 2025-08-07 [email protected] Adds deprecation for impeller opt out on android (flutter/flutter#173375) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

…ode 26+ (#173443) (#173472) Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request. ### Issue Link: Part 2 of #144218 ### Changelog Description: Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples Implementation of a future fix to allow Xcode 26 to `flutter run` twice in a row. ### Impact Description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch) Flutter developers running Xcode 26 can `flutter run` to a tethered iOS device once. However subsequent `flutter run` attempts are likely to fail. ### Workaround: Is there a workaround for this issue? Quitting and reopening Xcode. ### Risk: What is the risk level of this cherry-pick? ### Test Coverage: Are you confident that your fix is well-tested by automated tests? ### Validation Steps: What are the steps to validate that this fix works? Create a flutter project and run `flutter run` twice in a row with a physical iOS 17+ device and Xcode 26.

The previous integration test only tested one workflow, so I re-designed the test to be able to test both workflows and validate the correct commands are being used. Follow up to #173443. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

…lutter#173443) This PR introduces a new feature flag called `lldb-debugging`, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of `devicectl` and `lldb` to install, launch, and debug the app. If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation. This PR also adds analytics to track what deployment method is used and if it's successful. Part 2 and 3 of flutter#173416. Fixes flutter#144218. Fixes flutter#133465. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

…ode 26+ (#173443) (#173659) Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request. ### Issue Link: Part 2 of #144218 ### Changelog Description: Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples Use LLDB and devicectl for deploying to physical iOS devices when using Xcode 26. This will allow Xcode 26 to `flutter run` twice in a row. ### Impact Description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch) Flutter developers running Xcode 26 can `flutter run` to a tethered iOS device once. However subsequent `flutter run` attempts are likely to fail. ### Workaround: Is there a workaround for this issue? Quitting and reopening Xcode. ### Risk: What is the risk level of this cherry-pick? ### Test Coverage: Are you confident that your fix is well-tested by automated tests? ### Validation Steps: What are the steps to validate that this fix works? Create a flutter project and run `flutter run` twice in a row with a physical iOS 17+ device and Xcode 26.

…lutter#173443) This PR introduces a new feature flag called `lldb-debugging`, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of `devicectl` and `lldb` to install, launch, and debug the app. If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation. This PR also adds analytics to track what deployment method is used and if it's successful. Part 2 and 3 of flutter#173416. Fixes flutter#144218. Fixes flutter#133465. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

The previous integration test only tested one workflow, so I re-designed the test to be able to test both workflows and validate the correct commands are being used. Follow up to flutter#173443. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

…lutter#173443) This PR introduces a new feature flag called `lldb-debugging`, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of `devicectl` and `lldb` to install, launch, and debug the app. If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation. This PR also adds analytics to track what deployment method is used and if it's successful. Part 2 and 3 of flutter#173416. Fixes flutter#144218. Fixes flutter#133465. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

The previous integration test only tested one workflow, so I re-designed the test to be able to test both workflows and validate the correct commands are being used. Follow up to flutter#173443. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

…lutter#173443) This PR introduces a new feature flag called `lldb-debugging`, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of `devicectl` and `lldb` to install, launch, and debug the app. If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation. This PR also adds analytics to track what deployment method is used and if it's successful. Part 2 and 3 of flutter#173416. Fixes flutter#144218. Fixes flutter#133465. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

The previous integration test only tested one workflow, so I re-designed the test to be able to test both workflows and validate the correct commands are being used. Follow up to flutter#173443. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

…ode 26+ (flutter/flutter#173443)

…lutter#173443) This PR introduces a new feature flag called `lldb-debugging`, which is turned on by default. When this feature is turned on, if deploying to a physical iOS 17+ device with Xcode 26+, it will use a mixture of `devicectl` and `lldb` to install, launch, and debug the app. If LLDB fails, it will fallback to use Xcode automation. If LLDB times out, it will warn the user they may want to disable it. If LLDB is disabled, it will use Xcode automation. This PR also adds analytics to track what deployment method is used and if it's successful. Part 2 and 3 of flutter#173416. Fixes flutter#144218. Fixes flutter#133465. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

The previous integration test only tested one workflow, so I re-designed the test to be able to test both workflows and validate the correct commands are being used. Follow up to flutter#173443. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

vashworth added 2 commits August 7, 2025 17:50

Use LLDB as the default debugging method for iOS 17+

711a964

++

f81ecc8

github-actions bot added platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels. a: desktop Running on desktop team-ios Owned by iOS platform team labels Aug 7, 2025

gemini-code-assist bot reviewed Aug 7, 2025

View reviewed changes

packages/flutter_tools/lib/src/ios/devices.dart Show resolved Hide resolved

vashworth added 4 commits August 7, 2025 18:56

++

0e5a58c

++

f6aef05

++

25e2c53

++

b02a1f4

vashworth marked this pull request as ready for review August 8, 2025 00:21

vashworth requested review from a team and matanlurey as code owners August 8, 2025 00:21

vashworth requested review from bkonyi and removed request for matanlurey August 8, 2025 00:22

++

261be4b

vashworth changed the title ~~Use LLDB as the default debugging method for iOS 17+~~ Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ Aug 8, 2025

vashworth commented Aug 8, 2025

View reviewed changes

bkonyi approved these changes Aug 8, 2025

View reviewed changes

vashworth added the autosubmit Merge PR when tree becomes green via auto submit App label Aug 8, 2025

auto-submit bot added this pull request to the merge queue Aug 8, 2025

Merged via the queue into flutter:master with commit 3821790 Aug 8, 2025
154 checks passed

flutter-dashboard bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Aug 8, 2025

engine-flutter-autoroll mentioned this pull request Aug 8, 2025

Roll Flutter from 92a6bfbfd6ef to 38217906e95c (17 revisions) flutter/packages#9778

Merged

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Aug 8, 2025

38217906e Use LLDB as the default debugging method for iOS 17+ and Xc…

7fa966f

…ode 26+ (flutter/flutter#173443)

vashworth added the cp: beta cherry pick this pull request to beta release candidate branch label Aug 8, 2025

This was referenced Aug 8, 2025

Long-term solution to replacing ios-deploy #133465

Closed

Error starting debug session in Xcode: Timed out waiting for CONFIGURATION_BUILD_DIR to update. #144218

Closed

Piinks mentioned this pull request Aug 8, 2025

Flutter Notable Commits - 2025 #161460

Open

vashworth mentioned this pull request Aug 11, 2025

Update integration test for iOS deployment workflows #173566

Merged

9 tasks

reidbaker mentioned this pull request Oct 1, 2025

[CP] Flutter analyze --suggestions update for 3.35 #176359

Merged

9 tasks

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 12, 2025

38217906e Use LLDB as the default debugging method for iOS 17+ and Xc…

55255ae

…ode 26+ (flutter/flutter#173443)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ #173443

Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ #173443

Uh oh!

vashworth commented Aug 7, 2025 •

edited

Loading

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

Uh oh!

vashworth Aug 8, 2025

Uh oh!

vashworth Aug 8, 2025

Uh oh!

bkonyi left a comment

Uh oh!

bkonyi Aug 8, 2025

Uh oh!

Uh oh!

flutteractionsbot commented Aug 8, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	// Core Devices (iOS 17 devices) are debugged through Xcode so don't
	// include these flags, which are used to check if the app was launched
	// via Flutter CLI and `ios-deploy`.
	final List<String> filteredLaunchArguments = launchArguments
	.where((String arg) => arg != '--enable-checked-mode' && arg != '--verify-entry-points')
	.toList();

	Future<bool> _startAppOnCoreDevice({
	required DebuggingOptions debuggingOptions,
	required IOSApp package,
	required List<String> launchArguments,
	required String? mainPath,
	required ShutdownHooks shutdownHooks,
	@visibleForTesting Duration? discoveryTimeout,
	}) async {
	if (!debuggingOptions.debuggingEnabled) {
	// Release mode

	// Install app to device
	final bool installSuccess = await _coreDeviceControl.installApp(
	deviceId: id,
	bundlePath: package.deviceBundlePath,
	);
	if (!installSuccess) {
	return installSuccess;
	}

	// Launch app to device
	final bool launchSuccess = await _coreDeviceControl.launchApp(
	deviceId: id,
	bundleId: package.id,
	launchArguments: launchArguments,
	);

	return launchSuccess;
	} else {
	_logger.printStatus(
	'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.',
	);
	final launchTimeout = isWirelesslyConnected ? 45 : 30;
	final timer = Timer(discoveryTimeout ?? Duration(seconds: launchTimeout), () {
	_logger.printError(
	'Xcode is taking longer than expected to start debugging the app. '
	'Ensure the project is opened in Xcode.',
	);
	});

	XcodeDebugProject debugProject;
	final FlutterProject flutterProject = FlutterProject.current();

	if (package is PrebuiltIOSApp) {
	debugProject = await _xcodeDebug.createXcodeProjectWithCustomBundle(
	package.deviceBundlePath,
	templateRenderer: globals.templateRenderer,
	verboseLogging: _logger.isVerbose,
	);
	} else if (package is BuildableIOSApp) {
	// Before installing/launching/debugging with Xcode, update the build
	// settings to use a custom configuration build directory so Xcode
	// knows where to find the app bundle to launch.
	final Directory bundle = _fileSystem.directory(package.deviceBundlePath);
	await updateGeneratedXcodeProperties(
	project: flutterProject,
	buildInfo: debuggingOptions.buildInfo,
	targetOverride: mainPath,
	configurationBuildDir: bundle.parent.absolute.path,
	);

	final IosProject project = package.project;
	final XcodeProjectInfo? projectInfo = await project.projectInfo();
	if (projectInfo == null) {
	globals.printError('Xcode project not found.');
	return false;
	}
	if (project.xcodeWorkspace == null) {
	globals.printError('Unable to get Xcode workspace.');
	return false;
	}
	final String? scheme = projectInfo.schemeFor(debuggingOptions.buildInfo);
	if (scheme == null) {
	projectInfo.reportFlavorNotFoundAndExit();
	}

	_xcodeDebug.ensureXcodeDebuggerLaunchAction(project.xcodeProjectSchemeFile(scheme: scheme));

	debugProject = XcodeDebugProject(
	scheme: scheme,
	xcodeProject: project.xcodeProject,
	xcodeWorkspace: project.xcodeWorkspace!,
	hostAppProjectName: project.hostAppProjectName,
	expectedConfigurationBuildDir: bundle.parent.absolute.path,
	verboseLogging: _logger.isVerbose,
	);
	} else {
	// This should not happen. Currently, only PrebuiltIOSApp and
	// BuildableIOSApp extend from IOSApp.
	_logger.printError('IOSApp type ${package.runtimeType} is not recognized.');
	return false;
	}

	final bool debugSuccess = await _xcodeDebug.debugApp(
	project: debugProject,
	deviceId: id,
	launchArguments: launchArguments,
	);
	timer.cancel();

	// Kill Xcode on shutdown when running from CI
	if (debuggingOptions.usingCISystem) {
	shutdownHooks.addShutdownHook(() => _xcodeDebug.exit(force: true));
	}

	return debugSuccess;
	}
	}

	Future<(bool, IOSDeploymentMethod)> _startAppOnCoreDevice({
	required DebuggingOptions debuggingOptions,
	required IOSApp package,
	required List<String> launchArguments,
	required String? mainPath,
	required ShutdownHooks shutdownHooks,
	@visibleForTesting Duration? discoveryTimeout,
	}) async {
	if (!debuggingOptions.debuggingEnabled) {
	// Release mode

	// Install app to device
	final bool installSuccess = await _coreDeviceControl.installApp(
	deviceId: id,
	bundlePath: package.deviceBundlePath,
	);
	if (!installSuccess) {
	return (installSuccess, IOSDeploymentMethod.coreDeviceWithoutDebugger);
	}

	// Launch app to device
	final IOSCoreDeviceLaunchResult? launchResult = await _coreDeviceControl.launchApp(
	deviceId: id,
	bundleId: package.id,
	launchArguments: launchArguments,
	);
	final bool launchSuccess = launchResult != null && launchResult.outcome == 'success';

	return (launchSuccess, IOSDeploymentMethod.coreDeviceWithoutDebugger);
	}

	IOSDeploymentMethod? deploymentMethod;

	// Xcode 16 introduced a way to start and attach to a debugserver through LLDB.
	// However, it doesn't work reliably until Xcode 26.
	// Use LLDB if Xcode version is greater than 26 and the feature is enabled.
	final Version? xcodeVersion = globals.xcode?.currentVersion;
	final bool lldbFeatureEnabled = featureFlags.isLLDBDebuggingEnabled;
	if (xcodeVersion != null && xcodeVersion.major >= 26 && lldbFeatureEnabled) {
	final bool launchSuccess = await _coreDeviceLauncher.launchAppWithLLDBDebugger(
	deviceId: id,
	bundlePath: package.deviceBundlePath,
	bundleId: package.id,
	launchArguments: launchArguments,
	);

	// If it succeeds to launch with LLDB, return, otherwise continue on to
	// try launching with Xcode.
	if (launchSuccess) {
	return (launchSuccess, IOSDeploymentMethod.coreDeviceWithLLDB);
	} else {
	deploymentMethod = IOSDeploymentMethod.coreDeviceWithXcodeFallback;
	_analytics.send(
	Event.appleUsageEvent(
	workflow: 'ios-physical-deployment',
	parameter: IOSDeploymentMethod.coreDeviceWithLLDB.name,
	result: 'launch failed',
	),
	);
	}
	}

	deploymentMethod ??= IOSDeploymentMethod.coreDeviceWithXcode;

	// If LLDB is not available or fails, fallback to using Xcode.
	_logger.printStatus(
	'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.',
	);
	final launchTimeout = isWirelesslyConnected ? 45 : 30;
	final timer = Timer(discoveryTimeout ?? Duration(seconds: launchTimeout), () {
	_logger.printError(
	'Xcode is taking longer than expected to start debugging the app. '
	'If the issue persists, try closing Xcode and re-running your Flutter command.',
	);
	});

	XcodeDebugProject debugProject;
	final FlutterProject flutterProject = FlutterProject.current();

	if (package is PrebuiltIOSApp) {
	debugProject = await _xcodeDebug.createXcodeProjectWithCustomBundle(
	package.deviceBundlePath,
	templateRenderer: globals.templateRenderer,
	verboseLogging: _logger.isVerbose,
	);
	} else if (package is BuildableIOSApp) {
	// Before installing/launching/debugging with Xcode, update the build
	// settings to use a custom configuration build directory so Xcode
	// knows where to find the app bundle to launch.
	final Directory bundle = _fileSystem.directory(package.deviceBundlePath);
	await updateGeneratedXcodeProperties(
	project: flutterProject,
	buildInfo: debuggingOptions.buildInfo,
	targetOverride: mainPath,
	configurationBuildDir: bundle.parent.absolute.path,
	);

	final IosProject project = package.project;
	final XcodeProjectInfo? projectInfo = await project.projectInfo();
	if (projectInfo == null) {
	globals.printError('Xcode project not found.');
	return (false, deploymentMethod);
	}
	if (project.xcodeWorkspace == null) {
	globals.printError('Unable to get Xcode workspace.');
	return (false, deploymentMethod);
	}
	final String? scheme = projectInfo.schemeFor(debuggingOptions.buildInfo);
	if (scheme == null) {
	projectInfo.reportFlavorNotFoundAndExit();
	}

	_xcodeDebug.ensureXcodeDebuggerLaunchAction(project.xcodeProjectSchemeFile(scheme: scheme));

	debugProject = XcodeDebugProject(
	scheme: scheme,
	xcodeProject: project.xcodeProject,
	xcodeWorkspace: project.xcodeWorkspace!,
	hostAppProjectName: project.hostAppProjectName,
	expectedConfigurationBuildDir: bundle.parent.absolute.path,
	verboseLogging: _logger.isVerbose,
	);
	} else {
	// This should not happen. Currently, only PrebuiltIOSApp and
	// BuildableIOSApp extend from IOSApp.
	_logger.printError('IOSApp type ${package.runtimeType} is not recognized.');
	return (false, deploymentMethod);
	}

	// Core Devices (iOS 17 devices) are debugged through Xcode so don't
	// include these flags, which are used to check if the app was launched
	// via Flutter CLI and `ios-deploy`.
	final List<String> filteredLaunchArguments = launchArguments
	.where((String arg) => arg != '--enable-checked-mode' && arg != '--verify-entry-points')
	.toList();

	final bool debugSuccess = await _xcodeDebug.debugApp(
	project: debugProject,
	deviceId: id,
	launchArguments: filteredLaunchArguments,
	);
	timer.cancel();

	// Kill Xcode on shutdown when running from CI
	if (debuggingOptions.usingCISystem) {
	shutdownHooks.addShutdownHook(() => _xcodeDebug.exit(force: true));
	}

	return (debugSuccess, deploymentMethod);
	}

Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ #173443

Use LLDB as the default debugging method for iOS 17+ and Xcode 26+ #173443

Uh oh!

Conversation

vashworth commented Aug 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pre-launch Checklist

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

vashworth Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

vashworth Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

bkonyi left a comment

Choose a reason for hiding this comment

Uh oh!

bkonyi Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

flutteractionsbot commented Aug 8, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vashworth commented Aug 7, 2025 •

edited

Loading