-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flutter pub global activate devtools - The lower bound of "sdk: '>=2.1.0-dev <3.0.0'" must be 2.12.0 or higher to enable null safety. #7135
Comments
DevTools is shipped as part of the Dart and Flutter SDKs and is no longer shipped on pub. So when you upgrade Flutter, you automatically get the version of DevTools that is shipped with that SDK. We release monthly, so each Flutter beta and stable have a new version of DevTools. You can see the release notes here: https://docs.flutter.dev/tools/devtools/release-notes. If you run I'm going to close this issue since it is related to the legacy DevTools that is shipped on Pub. If you are experiencing issues with the Performance view in VS code, please file a separate issue with repro steps. A screenshot or screen recording would also be helpful. Thanks! |
Thanks for clarifying! Btw, I managed to get DevTools running by other methods. Still, the error specifically and the entire legacy situation with pub might be confusing for some, especially, if you follow older online guides and discussions. Maybe, there is a way to include a note when trying to launch it via pub... |
The package is discontinued on pub: https://pub.dev/packages/devtools, and IIRC we added a warning to the last published version of DevTools on pub which warned users that DevTools would no longer be published on pub and that they should switch to using DevTools directly from the Flutter SDK. Up to date docs on how to launch DevTools are on flutter.dev: https://docs.flutter.dev/tools/devtools/vscode. Would you mind sharing a link to the guides you were following that were referencing DevTools from pub? |
Many thanks for the explanation! Is there no possibility to include a legacy warning when running a command like >flutter pub global activate devtools to prevent this? I mean, now people hopefully will find this discussion here, but beforehand for an amateur user it was difficult to understand this. In any case, I will leave some comments later today on the stockoverflow pages that I visited and that pointed me towards using "flutter pub global activate devtools" to get it activated! |
Dear team, I want to update devtools in visual studio code because I have issues with the performance view (endless loading of the view). However, when running the recommended update command in terminal, I keep getting the following error:
Flutter seems fine:
Dart is of version 3.2.3.
My pubspec.yaml specifies:
Others have experienced the same issues, see here: flutter/flutter#123681. I could not find any solution online.
The text was updated successfully, but these errors were encountered: