Firebase functions:shell is ignoring emulator and using production instead

[risalfajar]

[REQUIRED] Environment info

firebase-tools: 11.15.0

Platform: Pop OS (Ubuntu)

[REQUIRED] Test case

The problem is not project-related.

[REQUIRED] Steps to reproduce

1. Create a Firebase project
2. Init a Firebase emulator (at least have Firestore and Functions)
3. Create a callable function that access Firestore to be tested
4. Start Firestore emulator
5. Start Functions shell
6. Call the function in point 3

[REQUIRED] Expected behavior

The function will affect Firestore in emulator

[REQUIRED] Actual behavior

The function affects Firestore in production

[taeold]

functions:shell command predates Firestore/Storage/other emulator and doesn't not attempt to spin them up as part of its command. You will need to use emulator:start with configurations for other emulators to get them up and running.

I think this request is a good feature request though - I'll track the issue as a feature request instead.

[risalfajar]

@taeold i have already started the emulators as in the steps number 4.

You can see in the screenshot above the "connected to firestore emulator...", But it actually calling firestore in production.

I think this is a bug.

[taeold]

AFAIK The Emulator suite works best when launched via emulator:start command. That way we know exactly what emalators are running and coordinate necessary changes to make sure that the emulated function calls the emulated service, not production ones.

I didn't think the setup you described where we have 2 process launching emalators ever worked because the functions emulator launched via functions:shell command wouldn't be able to know if Firestore emulator is running - and where.

Are you saying that this setup used to work in the past and no longer works now?

As for bug or feature request - I see why you'd call it a bug. It's just an attempt to prioritize things.

If we broke your existing, working setup with a recent release, yes we will definitely patch it asap.

As for others issues, we have to find time to work on them, and marking it as feature request is our best attempt to put some order to incoming, unplanned work! Sorry if this is disappointing.

[risalfajar]

@taeold I have 2 terminals opened with different command:

1. firebase emulators:start --import=./emulators-cache --export-on-exit --only "auth","firestore","database","pubsub","storage"
2. firebase functions:shell

What I am expecting is for the Shell to detect the emulator, and calling any function from it would affect the emulator only.

The Shell definitely knows that emulators are running (see screenshot above). But as soon as I call a function, it stopped detecting those emulators, hence calling the production.

[risalfajar]

Identical issue: #2116

Could you help @samtstern ?

[taeold]

@risalfajar Unfortunately for all of us, Sam no longer works at Firebase :(

Thanks for sharing more context - I didn't look at your initial screenshot carefully and yes it looks like things should've worked as you described as suggested by the log output. Sorry for confusion my part.

[risalfajar]

@taeold that's unfortunate 🙁

But I hope this is a quick fix since it have been fixed before.

[jlalvarez18]

I have the same issue:

functions: Connected to running firestore emulator at 127.0.0.1:8080, calls to this service will affect the emulator
⚠ functions: The following emulators are not running, calls to these services will affect production: database, pubsub, storage, eventarc

--- Invoke function here

⚠ functions: The Cloud Firestore emulator is not running, so calls to Firestore will affect production.

The above output states that it sees the emulator. When you invoke a function it then proceeds to hit production. This is a serious bug that needs to be resolved.