-
Notifications
You must be signed in to change notification settings - Fork 125
crash on near-empty package #2778
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
Comments
I don't know why some users seem to encounter this while others do not, that remains a bit of a mystery. Whether FLUTTER_ROOT is set is another question I have. We should be warning about that, but if the warning is broken it could lead to a problem here. |
What does near-empty mean? No |
`/Users/REDACTED/temp/dartdoc_bug_test# echo $FLUTTER_ROOT /Users/REDACTED/flutter_sdk/flutter` |
Near empty just meant that I haven't changed anything after running.
|
Ran into the same issue with flutter 2.2.3. Running
|
tl;dr; -- It's now working for me. I had to do a few steps I'll document below. As @abarisain said, I ran After that it worked on the flutter project created without any changes ( However, when I ran it on my "real" Flutter application it failed with:
I ran: That command failed on dartdoc with:
Then I deactivated the global dartdoc (which actually didn't do anything because it wasn't active at this point). Then I activated it again ( Ran Then ran dartdoc again and it worked. Hope this information helps. |
ok. That might explain why I can never seem to reproduce this problem as I tend to start from a clean Flutter install. I could add a blurb to the exception handler suggesting either flutter pub global activate or pub global activate... |
I'm hoping adding a message when this case comes up will help steer users toward a good place, see #2781 |
Nice! I was very confused the first time I upgraded flutter and the global package broke, this will be very helpful. I believe flutter should do like nvm and reinstall global packages on upgrade but that's out of scope here. Is dartdoc 3.0 compatible with dart 2.2.3 at all? I could swear that it was my first time installing it on my machine, so I couldn't have had a prior corrupted installation. |
dartdoc requires Dart 2.12 to run, but should still be able to interpret code written for 2.9. |
I know this is closed, but I just got it again. Thoughts?
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.5.2 20G95 darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.60.0)
[✓] Connected device (2 available)
• No issues found!
Steps:
Originally posted by @danfleck in #2594 (comment)
The text was updated successfully, but these errors were encountered: