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
Improve messaging when trying to connect to an app in release mode #4273
@johnpryan are you using current stable Flutter? I changed this message in 68cf41f but it requires flutter/flutter#106337 (in theory we might be able to check the mode another way, but since this is already I'm inclined to just wait for it to ship).
I will add a "More info" button that links to those docs though.
@johnpryan can you confirm exactly where we should link to? The link above seems to be related to profile mode, but this issue is only about release mode?
That's a good point, the Flutter performance profiling page isn't quite right because it's also common to use DevTools in Debug mode. I'm not sure we have a place in our docs that says DevTools should only be run in Debug or Profile mode, not Release mode.
Ah, in that case is there anything else to do here? The current message (when running on latest code) says:
DevTools is not available for an app running in this mode.
We could make this more specific (release/profile mode), however it requires making some assumptions in VS Code that I'd rather avoid (there are many ways the user could start the app in profile/release mode that are harder for us to detect).
I would prefer if it said "DevTools only supports Debug or Profile mode". The current gives two possible explanations, which can lead to confusion and doesn't tell the user how to resolve the issue.
Is there a way to detect that the debug session isn't ready yet so that we can disambiguate these two scenarios?
I would prefer if it said "DevTools only supports Debug or Profile mode".
Isn't it the case that profile mode for Web doesn't support DevTools (it doesn't have a VM Service)? (see flutter/devtools#3969 (comment)). If so, could it be confusing to say it's only available in debug/profile mode if the user is running a profile (web) build?
Is there a way to detect that the debug session isn't ready yet so that we can disambiguate these two scenarios?
That's what the changes above do. With the latest code (if you're using Flutter master (or beta?)) we will show the new message posted above if we know the debug session has started, and otherwise show the old one (from your screenshot). In a future release, we could drop the "or does not support DevTools" part from that last message so that last message is less vague.
This issue has been marked stale because it is tagged awaiting-info for 20 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days.
"DevTools is not available for [mode] mode on device [deviceId]" would definitely help here, the table at https://dart.dev/tools/dart-devtools is also handy, but doesn't contain any information about whether the user is in run/profile/release mode
It requires both flutter/flutter#121239 and a change here in the VS Code extension, so it'll still show the old message until you're using updated versions of each.
I haven't added a link to the page above for now, since it doesn't mention modes - however if it's reasonable for that page to be updated to mention modes, we could easily add a button here.
Activity
DanTup commentedon Nov 23, 2022
@johnpryan are you using current stable Flutter? I changed this message in 68cf41f but it requires flutter/flutter#106337 (in theory we might be able to check the mode another way, but since this is already I'm inclined to just wait for it to ship).
I will add a "More info" button that links to those docs though.
DanTup commentedon Nov 23, 2022
@johnpryan can you confirm exactly where we should link to? The link above seems to be related to profile mode, but this issue is only about release mode?
johnpryan commentedon Nov 23, 2022
That's a good point, the Flutter performance profiling page isn't quite right because it's also common to use DevTools in Debug mode. I'm not sure we have a place in our docs that says DevTools should only be run in Debug or Profile mode, not Release mode.
DanTup commentedon Nov 23, 2022
Ah, in that case is there anything else to do here? The current message (when running on latest code) says:
We could make this more specific (release/profile mode), however it requires making some assumptions in VS Code that I'd rather avoid (there are many ways the user could start the app in profile/release mode that are harder for us to detect).
johnpryan commentedon Nov 23, 2022
I would prefer if it said "DevTools only supports Debug or Profile mode". The current gives two possible explanations, which can lead to confusion and doesn't tell the user how to resolve the issue.
Is there a way to detect that the debug session isn't ready yet so that we can disambiguate these two scenarios?
DanTup commentedon Nov 23, 2022
Isn't it the case that profile mode for Web doesn't support DevTools (it doesn't have a VM Service)? (see flutter/devtools#3969 (comment)). If so, could it be confusing to say it's only available in debug/profile mode if the user is running a profile (web) build?
That's what the changes above do. With the latest code (if you're using Flutter master (or beta?)) we will show the new message posted above if we know the debug session has started, and otherwise show the old one (from your screenshot). In a future release, we could drop the "or does not support DevTools" part from that last message so that last message is less vague.
Dart-Code/src/extension/commands/debug.ts
Lines 137 to 147 in ecad283
johnpryan commentedon Nov 29, 2022
That's a good point, maybe we could link to a compatibility table in the docs or something...
Sounds good
johnpryan commentedon Nov 29, 2022
Related to flutter/devtools#4050
johnpryan commentedon Nov 29, 2022
I filed an issue to add a warning about web support flutter/website#7887
DanTup commentedon Nov 30, 2022
Is there an existing one I can link to? If not, if we can add one I can add a "more info" button here to link to it.
johnpryan commentedon Dec 6, 2022
No, I don't think we have a compatibility table in the docs right now.
13 remaining items
github-actions commentedon Mar 20, 2023
This issue has been marked stale because it is tagged awaiting-info for 20 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days.
johnpryan commentedon Mar 21, 2023
"DevTools is not available for [mode] mode on device [deviceId]" would definitely help here, the table at https://dart.dev/tools/dart-devtools is also handy, but doesn't contain any information about whether the user is in run/profile/release mode
[flutter_tools] Include mode in app.start event, and forward app.star…
DanTup commentedon Mar 30, 2023
Ok, I've updated so it'll look like this:
It requires both flutter/flutter#121239 and a change here in the VS Code extension, so it'll still show the old message until you're using updated versions of each.
I haven't added a link to the page above for now, since it doesn't mention modes - however if it's reasonable for that page to be updated to mention modes, we could easily add a button here.
Improve error message if Flutter tells us the mode/device it's runnin…