Generated pubspec.yaml has invalid YAML for font_awesome_flutter and page_transition (missing space after colon)

[LightworkerMark]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Every generated pubspec.yaml for this project consistently omits the space after the colon for two dependency entries -- font_awesome_flutter and page_transition -- producing invalid YAML:

font_awesome_flutter:11.0.0
page_transition:2.2.2

Valid YAML requires a space after the colon (every other dependency in the same file is formatted correctly -- only these two consistently come out malformed):

font_awesome_flutter: 11.0.0
page_transition: 2.2.2

This breaks flutter pub get wherever the generated project is built. It has reproduced on every single export across an extended session (not intermittent), and it also breaks FlutterFlow's own backend builds: a Test Pilot run against this project failed outright (0 tests executed) with the same YAML parse error, sourced from FlutterFlow's own build scratch directory (/tmp/ff_service_scratch/.../enlighten_me/pubspec.yaml). That confirms this isn't just a quirk of one local export path -- it's baked into whatever codegen step produces pubspec.yaml for this project, and it affects FlutterFlow's own backend services (Test Pilot Run ID: CAz3dPIbf1fMglhbsmCt).

Full error from the Test Pilot build failure:

Error: Command failed: cd /tmp/ff_service_scratch/mCogi3F3Mg7rF21Vl6ic/enlighten_me && flutter pub get
Unhandled exception:
Error on line 102, column 3: Expected ':'.
╷
102 │ from_css_color: 2.0.0
│ ^
╵
#0 Scanner._reportError (package:yaml/src/scanner.dart:1639:7)
#1 Scanner._staleSimpleKeys (package:yaml/src/scanner.dart:485:9)
#2 Scanner._fetchMoreTokens (package:yaml/src/scanner.dart:319:9)
#3 Scanner.peek (package:yaml/src/scanner.dart:311:27)
#4 Parser._parseBlockMappingKey (package:yaml/src/parser.dart:424:26)
#5 Parser._stateMachine (package:yaml/src/parser.dart:100:16)
#6 Parser.parse (package:yaml/src/parser.dart:61:19)
#7 Loader._loadMapping (package:yaml/src/loader.dart:169:23)
#8 Loader._loadNode (package:yaml/src/loader.dart:88:35)
#9 Loader._loadMapping (package:yaml/src/loader.dart:163:19)
#10 Loader._loadNode (package:yaml/src/loader.dart:88:35)
#11 Loader._loadDocument (package:yaml/src/loader.dart:68:20)
#12 Loader.load (package:yaml/src/loader.dart:60:20)
#13 loadYamlDocument (package:yaml/yaml.dart:69:25)
#14 loadYamlNode (package:yaml/yaml.dart:54:5)
#15 loadYaml (package:yaml/yaml.dart:41:5)
#16 FlutterManifest.createFromString (package:flutter_tools/src/flutter_manifest.dart:45:28)
#17 FlutterManifest.createFromPath (package:flutter_tools/src/flutter_manifest.dart:39:28)

(The parser reports the error at line 102, from_css_color: 2.0.0, which is itself correctly formatted -- that's just where the scanner's lookahead first detects the mapping is broken. The actual malformed line, font_awesome_flutter:11.0.0, sits immediately above it at line 101.)

Related issues suggesting this is a recurring pattern in the pubspec generator, not a one-off: #4361 (a different trigger -- an empty custom-code dependency -- produces the same class of invalid-YAML pubspec, confirmed since Oct 2024, with a maintainer comment saying it would be forwarded to engineering) and #7399 (a different bug -- a Dart type incompatibility, not a YAML syntax error -- but same package and version, font_awesome_flutter 11.0.0).

Working around it locally (manually re-inserting the missing space in an exported file) does not help -- FlutterFlow regenerates its own copy independently, confirmed by the Test Pilot failure happening against a freshly generated copy in FlutterFlow's own scratch directory, unaffected by any local fix.

Expected Behavior

Every dependency line in the generated pubspec.yaml should be valid YAML -- a space after the colon separating the package name and version, matching every other dependency in the file. flutter pub get should succeed against the generated file, both locally and in FlutterFlow's own hosted build/Test Pilot pipeline.

Steps to Reproduce

Step 1: Export/refresh this project's generated code (e.g. via the FlutterFlow AI SDK's flutterflow ai run / refresh-context, a normal project export, or a Test Pilot run -- any path that generates pubspec.yaml).
Step 2: Inspect the generated pubspec.yaml.
Step 3: Observe that the font_awesome_flutter and page_transition lines are missing the space after their colon, while every other dependency line has it.
Step 4: Run flutter pub get (or let any build pipeline run it) against that file.
Step 5: Observe the YAML parse failure described above.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4ok8nf8Y92xOUA7qqMbcFVmSQsQ2Ika7gJkspBZywgfZzzBLN/fPfQP1pCXf3kSghIMWKcp14EwcrnieDiUMY6CzWZRoR41aoBeDnKJWOlMqmTF7qgQUdTHcBUGn7Cyrejsx1NC7N0WiU67WCbetmyVgLAQa7NPEQ8Sq/LZO4=

Visual documentation

The bug was found in the base code by Claude code

Environment

FlutterFlow version: not captured directly (bug reproduced via the FlutterFlow AI SDK and via a FlutterFlow-hosted Test Pilot run, not the web editor)
Platform: FlutterFlow AI SDK (CLI codegen/export) and FlutterFlow's hosted Test Pilot build backend
Browser name and version: N/A -- not encountered via the web editor
Operating system and version affected: Windows 11 (local machine); FlutterFlow's own Test Pilot build environment (Linux container at /tmp/ff_service_scratch/...) for the server-side reproduction

Additional Information

No response

[LightworkerMark]

Additional data point: this also breaks FlutterFlow Desktop's local run feature, not just codegen export and Test Pilot.

After restarting FlutterFlow Desktop and starting a local run, flutter pub get failed with the exact same error, on the same two lines (same as the Current Behavior section above -- font_awesome_flutter and page_transition missing the space after the colon).

Notably, when I inspected the pubspec.yaml copies on disk right after this failure -- both FlutterFlow Desktop's own local-run workspace copy and the FlutterFlow AI SDK workspace copy -- both showed the font_awesome_flutter and page_transition lines correctly formatted (space after the colon). That suggests a race: the codegen step writes the malformed YAML first, flutter pub get runs against that malformed file, and a later regeneration/refresh pass rewrites the file correctly -- so by the time anyone inspects the file afterward, it looks fine again. This would explain why the file appears intermittently valid on manual inspection while the build step itself still fails consistently.

So this now reproduces across three separate paths, all hitting the same two lines:
Path 1: Local FlutterFlow AI SDK export/refresh (original report)
Path 2: FlutterFlow's own hosted Test Pilot build (/tmp/ff_service_scratch/.../pubspec.yaml)
Path 3: FlutterFlow Desktop's local run pipeline (this comment)

This points more strongly at the shared codegen step that emits pubspec.yaml, rather than anything specific to one build path.