[bug]: FlutterFire CLI writes Flutter metadata into firebase.json, breaking Firebase CLI with schema validation errors

[TheDevSaga]

Is there an existing issue for this?

• I have searched the existing issues.

CLI Version

1.3.1

Firebase Tools version

15.5.1

Flutter Doctor Output

[✓] Flutter (Channel stable, 3.38.9, on macOS 26.2 25C56 darwin-arm64, locale en-IN) [535ms]
• Flutter version 3.38.9 on channel stable at /Users/sagararora/src/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 67323de285 (13 days ago), 2026-01-28 13:43:12 -0800
• Engine revision 587c18f873
• Dart version 3.10.8
• DevTools version 2.51.1
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets, omit-legacy-version-file,
enable-lldb-debugging

[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0) [2.4s]
• Android SDK at /Users/sagararora/Library/Android/sdk
• Emulator version 36.3.10.0 (build_id 14472402) (CL:N/A)
• Platform android-36, build-tools 36.0.0
• ANDROID_HOME = /Users/sagararora/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: flutter config --jdk-dir="path/to/jdk".
• Java version OpenJDK Runtime Environment (build 21.0.8+-14196175-b1038.72)
• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 26.2) [1,425ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 17C52
• CocoaPods version 1.16.2

[✓] Chrome - develop for the web [7ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

Description

FlutterFire CLI generates or writes Flutter-specific metadata into firebase.json under a top-level flutter key.

However, firebase.json is strictly validated by the Firebase CLI, which does not allow unknown top-level properties. As a result, any Firebase CLI command fails, including:

firebase login

firebase projects:list

firebase deploy

This effectively bricks the Firebase CLI when FlutterFire metadata is present in firebase.json.

Steps to reproduce

just run the command

firebase login --debug

Its giving the error
Object "" in "firebase.json" has unknown property: {"additionalProperty":"flutter"}

Due to which firebase is not able refresh its token when expire

Expected behavior

FlutterFire CLI should not write Flutter-specific metadata into firebase.json

firebase.json should remain Firebase CLI–owned infrastructure config only

FlutterFire metadata should be stored in:

a separate file (e.g. flutterfire.json, .flutterfire/config.json)

or internal FlutterFire CLI state

Firebase CLI should remain usable after FlutterFire setup

Screenshots

No response

Additional context and comments

No response