Skip to content

Wish for the flutter tool to help the user switch to USB instead of WiFi when running/debugging against iOS 26 #176206

Closed

Description

@sethladd

Use case

Due to architectural changes from iOS 26, running/debugging a Flutter app during development against an iOS 26 iPhone connected to the host development machine via WiFi can be quite slow. We've noticed that the latency is felt most when the target device is connected over WiFi.

Proposal

We propose to detect when people are using iOS 26 devices connected via WiFi, and suggest to them to instead use a wired (USB) connection.

We propose to deliver this feedback via the flutter tool, and our IDE plugins. But, this issue specifically is for the flutter tool.

Activity

  1. vashworth commented on Sep 29, 2025

    @vashworth
    Contributor

    Agreed.

    We will need to add a warning to the top of this method:

    Future<LaunchResult> startApp(
    IOSApp package, {
    String? mainPath,
    String? route,
    required DebuggingOptions debuggingOptions,
    Map<String, Object?> platformArgs = const <String, Object?>{},
    bool prebuiltApplication = false,
    String? userIdentifier,
    @visibleForTesting Duration? discoveryTimeout,
    @visibleForTesting ShutdownHooks? shutdownHooks,
    }) async {

    Code would probably be something this

    if (isWirelesslyConnected &&
            debuggingOptions.debuggingEnabled && (sdkVersion != null || sdkVersion! >= Version(26, 0, null)) {
     _logger.printWarning(
         `Wireless debugging on iOS 26 may be slow. Consider using a wired connection.` // or something like that
        );
    }
    
  2. DanTup commented on Sep 29, 2025

    @DanTup
    Contributor

    I'm not sure if _logger.printWarning already surfaces something when run with --machine, but if not we should try to add something so that this warning can be provided (in a structured way) to the IDEs. That way they could show a more prominent warning than just a line of text in the console output.

  3. okorohelijah commented on Sep 29, 2025

    @okorohelijah
    Contributor

    @DanTup In the pr #176235 I emitted an event for the warning(see image below as a proposed event detail). If not, please lmk what details you'd like to be included in the event

    Image
  4. AlexV525 commented on Sep 30, 2025

    @AlexV525
    Member

    Could we do this for all wireless-connected devices? We have previously #144634, which is also unresolved.

  5. added a commit that references this issue on Oct 8, 2025
    2586c9c
  6. sethladd commented on Oct 8, 2025

    @sethladd
    ContributorAuthor

    Thank you!

  7. added 2 commits that reference this issue on Oct 13, 2025
    0c254f4
    23f80d7
  8. github-actions commented on Oct 22, 2025

    @github-actions

    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.

  9. locked as resolved and limited conversation to collaborators on Oct 22, 2025
  10. added a commit that references this issue on Dec 10, 2025
    f15c741
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions