cannot disconnect function from emulator after using connectFunctionsEmulator

[Yukinosuke-Takada]

Operating System

macOS 14.0

Browser Version

Chrome Version 117.0.5938.149 (Official Build) (arm64)

Firebase SDK Version

firebase v 10.7.0, @firebase/functions v 0.11.0

Firebase SDK Product:

Functions

Describe your project's tooling

I'm using firebase/function in my webapp.

My mac is running node v19.7.0, yarn 1.22.19

Describe the problem

I have a web app that tests Firebase functions. It tests the onCall function on the Emulator and Deployed in the same run. After using connectFunctionsEmulator(), The specified function will use the Emulator afterward (even if I don't call connectFunctionsEmulator).

Steps and code to reproduce issue

Code:

  const invokeWithFunctionName = async (
    environment: Environment,
    functionRegion: string,
    functionName: string,
    sendingParameters: Record<string, string>
  ) => {
    const firebaseFunctions: Functions = getFunctions(currentApp, functionRegion);
    if (environment === 'Emulator') {
      connectFunctionsEmulator(firebaseFunctions, 'localhost', 5001);
    } else {
      // disconnect emulator
      
    }
    const callable = httpsCallable(firebaseFunctions, functionName, { timeout: 10000 });
    const res = await callable(sendingParameters);
    return (res.data as string);
  };

await invokeWithFunctionName('Deployed', 'asia-northeast1', 'f', {});
await invokeWithFunctionName('Emulator', 'asia-northeast1', 'f', {});
await invokeWithFunctionName('Deployed', 'asia-northeast1', 'f', {});

The POST request it's sending

POST https://asia-northeast1-****.cloudfunctions.net/f
POST http://localhost:5001/****/asia-northeast1/f
POST http://localhost:5001/****/asia-northeast1/f

See that the 3rd POST request is stuck with using localhost.

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[looptheloop88]

Hi @Yukinosuke-Takada, thanks for bringing this matter to our attention. I was able to replicate the same behavior that you reported. Let me check with the team if there’s a way to disconnect from the Emulator programmatically.

[hsubox76]

So this isn't a very official way to do it but I think you should be able to do this: firebaseFunctions.emulatorOrigin = null and that should reset it back to the way it was before calling connectFunctionsEmulator().

I don't think we ever thought of this use case because we assumed people would run emulator tests in one process and non-emulator tests in a separate process. We could try to provide a more official way to do this if there is demand, but at the moment I think this is a somewhat uncommon use case and there is (maybe) a workaround. Also I don't think any of the other connect[Product]Emulator methods allow this, so we'd have to try to make it consistent.

Anyway let me know if that works, if it doesn't I'll look into it further.

[Yukinosuke-Takada]

Hi, thanks for the response.

I modified my code like this:

if (environment === 'Emulator') {
  connectFunctionsEmulator(firebaseFunctions, 'localhost', 5001);
} else {
  // disconnect emulator
  firebaseFunctions.emulatorOrigin = null;  // <- Error here
}

But I get error: Property 'emulatorOrigin' does not exist on type 'Functions'.

It seems the type Functions does not have the method .emulatorOrigin. Looking at the source code, type FunctionService has this method instead. I tried to type cast like (firebaseFunctions as FunctionService).emulatorOrigin = null; but, FunctionService seems not to be exported.