VS Code does NOT print output in debug console any more on Macbook M1
See original GitHub issueSteps to Reproduce
Unfortunately, I cannot reproduce this issue on the default counter app. It happens in my app which is quite robust. Some prints work, some never. Everything worked fine until Aug 12. I took a break from coding for a week and didn’t touch my computer for a week. Aug 19 is the first day, this issue started to appear. Everything works fine in Android Studio, though.
Expected results:
Actual results:
Logs
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.2.2 20D80 darwin-arm, locale
en-US)
• Flutter version 2.2.3 at /Users/tomasbaran/code/flutter
• Framework revision f4abaa0735 (7 weeks ago), 2021-07-01 12:46:11 -0700
• Engine revision 241c87ad80
• Dart version 2.13.4
[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
• Android SDK at /Users/tomasbaran/Library/Android/sdk
• Platform android-31, build-tools 31.0.0
• Java binary at: /Library/Internet
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
• Java version Java(TM) SE Runtime Environment (build 1.8.0_301-b09)
✗ Android licenses not accepted. To resolve this, run: flutter doctor
--android-licenses
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.5.1, Build version 12E507
• CocoaPods version 1.10.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[!] Android Studio (not installed)
• Android Studio not found; download from
https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup
for detailed instructions).
[✓] VS Code (version 1.59.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.25.0
[✓] Connected device (2 available)
• iPhone 12 Pro (mobile) • 52B1B8E2-0A95-4737-B3E8-62BB977671D9 • ios
• com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
• Chrome (web) • chrome •
web-javascript • Google Chrome 92.0.4515.159
! Error: Errors were encountered while preparing your device for
development. Please check the Devices and Simulators Window. (code -1)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:22 (10 by maintainers)
Top Results From Across the Web
C program not running in VSCode Macbook M1 - Stack Overflow
The output runs on the debug console. This is my sample code. The settings for compiler show CLang,GCC build and lldb.
Read more >Playground not displaying output | Apple Developer Forums
Am using Xcode 6 on old MacBook Pro and trying playground with swift - find that the output I expect is not being...
Read more >Debugging in Visual Studio Code
To run or debug a simple app in VS Code, select Run and Debug on the Debug start view or press F5 and...
Read more >Debugging with Visual Studio for Mac - Microsoft Learn
Visual Studio for Mac uses the Mono Soft Debugger to debug managed (C# or F#) code in all Xamarin applications. The Mono Soft...
Read more >Python with Visual Studio Code on macOS - Medium
By using the Python extension, you make VS Code into a great lightweight ... You can also work with variables in the Debug...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found the issue. I’m so sorry about this stupid mistake. I was filtering out a text and forgot about it that’s why it didn’t show other print outs. I’m ashamed :S
Thanks for testing! If it seems ok with that line, then it probably wasn’t a difference in the debug adapter being used (you can remove this line now you’ve tested).
If it does come up again, please do file an issue and we can try to do some more troubleshooting and capture a log.
Thanks!