Should I use sudo to install it?

No. dart pub global activate installs into your user’s pub cache. Running it with sudo puts it under the root user’s cache, which your normal shell doesn’t see.

Dart says pub global is legacy. Does that matter?

Not for this. The Firebase setup guide still uses dart pub global activate. If you install tools with dart install instead, they go to $DART_DATA_HOME/install/bin, so add that folder to PATH. If PUB_CACHE is set, the pub cache bin folder is inside that location instead.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

“flutterfire” Not Recognized or Not Found: Fix

Firebase setup errorFlutterFire: “flutterfire: command not found” / “The term ‘flutterfire’ is not recognized”

You run flutterfire configure and the terminal says command not found (or, in PowerShell, the term flutterfire is not recognized as the name of a cmdlet). The FlutterFire CLI is installed into Dart’s pub cache, and that cache’s bin folder isn’t on your PATH, or the CLI was never activated on this machine.

Short answer

Run dart pub global activate flutterfire_cli. Then add the pub cache bin folder to PATH: $HOME/.pub-cache/bin on macOS and Linux (in ~/.zprofile or ~/.bashrc), %LOCALAPPDATA%\Pub\Cache\bin on Windows. Close and reopen the terminal and editor, then run flutterfire configure. As a quick workaround, dart pub global run flutterfire_cli:flutterfire configure runs it without PATH.

Why the shell can’t find flutterfire, and the fix

01
The CLI was never activated on this machine
“Install the FlutterFire CLI by running the following command from any directory: dart pub global activate flutterfire_cli” Firebase, Add Firebase to your Flutter app
The FlutterFire CLI isn’t part of Flutter or the Firebase CLI. Activate it once per machine, from any folder.
```
dart pub global activate flutterfire_cli
```
02
The pub cache bin folder isn’t on PATH
“Verify that the bin directory for the system cache is in your path.” Dart, dart pub global
The activate command prints a warning when this folder is missing from PATH, and it is easy to miss. Add it, then close and reopen every terminal and your editor so they read the new PATH.
```
# macOS (zsh): add to ~/.zprofile
export PATH="$PATH:$HOME/.pub-cache/bin"

# Windows: add this folder to the Path user variable
%LOCALAPPDATA%\Pub\Cache\bin
```
03
You need it working right now
dart pub global run starts an activated package without PATH. It’s fine for a one-off configure; fix PATH for everyday use.
```
dart pub global run flutterfire_cli:flutterfire configure
```
04
flutterfire runs, then fails on the Firebase CLI
flutterfire configure calls the Firebase CLI to list your projects. If firebase isn’t installed or you aren’t logged in, it stops there. Install the Firebase CLI, run firebase login, and try again.
```
npm install -g firebase-tools
firebase login
flutterfire configure
```

Checked against the vendor’s docs on November 8, 2026: Firebase: Add Firebase to your Flutter app; Dart: dart pub global (PATH and pub cache).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Firebase setup errorFlutterFire: “flutterfire: command not found” / “The term ‘flutterfire’ is not recognized”

Why the shell can’t find flutterfire, and the fix

The CLI was never activated on this machine

The pub cache bin folder isn’t on PATH

You need it working right now

flutterfire runs, then fails on the Firebase CLI

Rather hand it over?

More on this error

Describe it and get a written quote