Flutter extension daemon not loading in Antigravity IDE

Google AI Studio
1

The agent seems to think this is related to Antigravity IDE itself, and we cannot find the source of the issue. Here the final conclusion of the Agent. Log file raw error is at bottom

Based on the persistent error mentioning line 216 when your file only has 65 lines, and given that

flutter pub get

works fine, this appears to be abug in Antigravity IDE’s Flutter extensionrather than an actual issue with your project.

Recommended Solutions:

Option 1: Use the command line for Flutter operations Your Flutter installation is working perfectly via command line. You can continue development using:

  • flutter run

    to run your app

  • flutter test

    for testing

  • The Dart analyzer is still working in Antigravity

Option 2: Try opening the project in VS Code If you have VS Code installed, try opening the same project there to see if the Flutter extension works properly.

Option 3: Report to Antigravity team This appears to be a bug in how Antigravity’s Flutter Daemon integration handles the pubspec parsing. The daemon is somehow seeing a different version of your pubspec.yaml file with 216+ lines.

For now, would you like me to help you run the app from the command line, or would you prefer to investigate the Antigravity extension issue further?

Log file

#0 Loader._loadMapping (package:yaml/src/loader.dart:165:9)
#1 Loader._loadNode (package:yaml/src/loader.dart:88:35)
#2 Loader._loadMapping (package:yaml/src/loader.dart:163:19)
#3 Loader._loadNode (package:yaml/src/loader.dart:88:35)
#4 Loader._loadDocument (package:yaml/src/loader.dart:68:20)
#5 Loader.load (package:yaml/src/loader.dart:60:20)
#6 loadYamlDocument (package:yaml/yaml.dart:69:25)
#7 loadYamlNode (package:yaml/yaml.dart:54:5)
#8 loadYaml (package:yaml/yaml.dart:41:5)
#9 FlutterManifest.createFromString (package:flutter_tools/src/flutter_manifest.dart:45:28)
#10 FlutterManifest.create…
[12:00:18 PM] [FlutterDaemon] [Warn] Prompting to reload: (The Flutter Daemon failed to start. Please review the log and file an issue on GitHub.) (actions: Restart Extension, Show Log)

5

Hello @hamtown15,

Thank you for reporting this. The Flutter Daemon failing to initialize effectively disables all language features (IntelliSense, Hot Reload, etc.), which is certainly a blocking issue.

Could you please check the following?

  • Open the Output panel (View > Output) and switch the dropdown menu from “Tasks” to “Flutter” or “Dart”. Do you see a specific error code or a “Process terminated” message there?
  • Go to Settings (Ctrl+,) and search for flutter.sdkPath. If this is empty, try manually setting it to the absolute path where Flutter is installed in your environment (e.g., /home/user/flutter or C:\src\flutter).
  • Ensure your project folder is in “Trusted” mode, as the Flutter Daemon is often blocked from spawning processes in Restricted Mode.
6

Thank you for the assist! When I try the dropdown for tasks, there is only an option for “flutter daemon”. It is currently showing just two dashes every time it tries to start. The problem though is that i cannot keep this output view open while i recreate the error, which only occurs immediately after I replicate the flutter app code repository.

Note I am running Antigravity on Mac. I updated the settings.json file with:

“dart.flutterSdkPath”: “~/Dev/flutter/”,

and restarted Antigravity, but the error remains. I have reviewed the logfile and i believe the PATH is correct for Flutter installation directory. Here is the pastebin link for the log file : pastebin

I can’t seem to find settings to verify the Trusted Mode contains my project folder. How would I do this?

8

Hi @hamtown15,

To make a project folder in Trusted Mode, please try the following steps:

  1. Open Antigravity.

  2. Press Cmd + Shift + P to open the Command Palette in your Mac.

  3. Type “Manage Workspace Trust” and select it.

  4. In the window that appears, look for the “Trusted Folders & Workspaces” section.

  5. Click the Add Folder button.

  6. Select the project folder you want to trust from your file system.

  7. Click Trust Folder to confirm.