Flutter debug always disconnect in version 0.40.4

I updated from 0.40.3 to 0.40.4 today and then, Flutter debug always disconnects suddenly without warning. There are no error messages in either the debug console or output, and I don’t know the reason. Version 0.40.3 doesn’t have this issue. If possible, I hope you can provide downloads for previous versions to temporarily resolve this problem. I’ll wait for you to fix this issue and update the version before I update to the latest version.

Below are the links to download 0.40.3. Could you please let me know if the problem is fixed after downgrading? Could you also send more details about the problem — do you see any logs in the Output tab for example?

Windows: https://downloader.cursor.sh/builds/240829epqamqp7h/windows/nsis/x64
Linux: https://downloader.cursor.sh/builds/240829epqamqp7h/linux/appImage/x64
MacOS Apple Silicon: https://downloader.cursor.sh/builds/240829epqamqp7h/mac/dmg/arm64
MacOS Intel: https://downloader.cursor.sh/builds/240829epqamqp7h/mac/dmg/x64

After extensive experimentation, I discovered that the issue arose because the Flutter and Dart plugins were automatically updated along with the upgrade. The problem was specifically related to the new versions of these two plugins. After downgrading these plugins, I found that the issue was resolved.

Therefore, this problem is not related to the new version of Cursor. Thank you for your assistance.

The previous versions of both the Flutter and Dart plugins were v3.94.0.

Thank you so much for investigating and confirming!

Hi, I’m having the same problem (debugging with flutter and when hitting a breakpoint either immediately or a couple of seconds later Cursor disconnects from the flutter app).

I’ve tried downgrading Cursor which didn’t work, and I’ve also tried downgrading the Flutter and dart extensions within Cursor to 3.98.0.

Interestingly it all works fine in VS Code Insiders with the most recent version of the extensions.

I first noticed this issue earlier a couple of days ago but at that point it would only crash when debugging a specific part of my code so I ignored it, now it crashes if I place breakpoints anywhere. Before first noticing it earlier in the week all was fine and I’d debugged the same Flutter app many times.

@frozy does debugging still work ok for you?

@arvid220u any thoughts on what could be causing it?

I’d really like go get it working again as going back to vscode has made me realise the productivity increase I get through Cursor.

Thanks