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
Wish to inform the user to prefer USB over WiFi when developing against an iOS 26 device #5730
We propose to inform the user that if they are running against an iOS 26 device and connected over WiFi, that we suggest to the user to instead connect their device via USB.
I think we should let the flutter tool drive this, because I don't think we know if the device is wireless from Dart-Code, and it'd be good to avoid hard-coding this logic.
The suggestion is to use _logger.printWarning in the tool - once that's done, I'll verify if this comes through in --machine mode and we can wire it up to a standard toast warning in Dart-Code (which would be more visible than just having it go by in the console output).
This requires an additional change in the Flutter debug adapter (to forward the warning on from flutter run to the DAP client) as well as the Dart-Code work.
It will look like this:
We also have support for a "More Info" URL which this warning doesn't currently provide, but would add a button like this:
@sethladd yes sorry - I don't have an iOS device so when I tested it I just commented out the check in the Flutter tool and I misread it as applying to < 26, so I had hard-coded 25 as my test version :-)
In reality, it will actually only trigger for iOS versions >= 26 and it will include your actual version in the message (which will be 26 or higher).
This is merged for the next Dart-Code release, however it relies on the Flutter changes to be triggered (those changes were unfortunately made after the recent beta cut).
This is merged for the next Dart-Code release, however it relies on the Flutter changes to be triggered (those changes were unfortunately made after the recent beta cut).
Activity
sethladd commentedon Sep 29, 2025
you could wait for flutter/flutter#176206 to be resolved, to either leverage the
flutter toolor borrow whatever messaging it uses for the user.DanTup commentedon Sep 29, 2025
I think we should let the
fluttertool drive this, because I don't think we know if the device is wireless from Dart-Code, and it'd be good to avoid hard-coding this logic.The suggestion is to use
_logger.printWarningin the tool - once that's done, I'll verify if this comes through in--machinemode and we can wire it up to a standard toast warning in Dart-Code (which would be more visible than just having it go by in the console output).DanTup commentedon Oct 10, 2025
This requires an additional change in the Flutter debug adapter (to forward the warning on from
flutter runto the DAP client) as well as the Dart-Code work.It will look like this:
We also have support for a "More Info" URL which this warning doesn't currently provide, but would add a button like this:
Add support for showing app warnings from Flutter
[tool/dap] Forward app.warning events from Flutter to DAP client
DanTup commentedon Oct 10, 2025
DAP work is open at flutter/flutter#176827
The Dart-Code work is currently on a branch at https://github.com/Dart-Code/Dart-Code/tree/show-app-warnings
sethladd commentedon Oct 10, 2025
Should the screenshot say ios 26?
DanTup commentedon Oct 10, 2025
@sethladd yes sorry - I don't have an iOS device so when I tested it I just commented out the check in the Flutter tool and I misread it as applying to < 26, so I had hard-coded 25 as my test version :-)
In reality, it will actually only trigger for iOS versions >= 26 and it will include your actual version in the message (which will be 26 or higher).
[tool/dap] Forward app.warning events from Flutter to DAP client (#17…
sethladd commentedon Oct 10, 2025
Ah, great! :)
DanTup commentedon Oct 13, 2025
This is merged for the next Dart-Code release, however it relies on the Flutter changes to be triggered (those changes were unfortunately made after the recent beta cut).
sethladd commentedon Oct 13, 2025
Thanks for following up, I appreciate it!
jmagman commentedon Oct 13, 2025
Beta cherry-pick here: flutter/flutter#176976
DanTup commentedon Oct 13, 2025
@jmagman if the plan is to cherry-pick this, we'll also need to do flutter/flutter#176827. Is it just a case of adding the tag to that PR?
(if so, feel free to add - it's late here so I won't be around long... otherwise if there's more to it, I can pick it up in the morning.. thanks!)
[tool/dap] Forward app.warning events from Flutter to DAP client (flu…
DanTup commentedon Oct 14, 2025
I added
cp:betato that change and the cherry-pick request for it is at flutter/flutter#176997.[CP-beta]Add structured warning event for slow wireless debugging on …
[CP-beta][tool/dap] Forward app.warning events from Flutter to DAP cl…
[tool/dap] Forward app.warning events from Flutter to DAP client (flu…
[tool/dap] Forward app.warning events from Flutter to DAP client (#17…