You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mac_ios ios_debug_workflow failing after https://github.com/flutter/flutter/pull/189993 #191138
Which causes a non-zero exit code. Since we're killing the process, I don't think the exit code really matters. Technically yeah, the app failed to launch because the test kills it on purpose.
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 -v and a minimal reproduction of the issue.
Activity
vashworth commentedon Aug 14, 2026
Okay so the test is failing because we're now killing lldb and devicectl on shutdown:
flutter/packages/flutter_tools/lib/src/ios/core_devices.dart
Lines 155 to 162 in f4228d7
And because mDNS doesn't work in CI, the Dart VM discovery stuff ends immediately:
flutter/packages/flutter_tools/lib/src/ios/devices.dart
Lines 982 to 987 in f4228d7
And returns a failure:
flutter/packages/flutter_tools/lib/src/ios/devices.dart
Lines 811 to 821 in f4228d7
Which causes a non-zero exit code. Since we're killing the process, I don't think the exit code really matters. Technically yeah, the app failed to launch because the test kills it on purpose.
flutter/dev/devicelab/bin/tasks/ios_debug_workflow.dart
Line 118 in f4228d7
Actually, we should just remove this test since lldb/devicectl is the default now.
Remove ios_debug_workflow test (flutter#191141)
jtmcdole commentedon Aug 18, 2026
Note to self: even though the test was removed, the closing of this bug un-spressed it (yay, it works):
github-actions commentedon Sep 1, 2026
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.