firebase / firebase/firebase-admin-java

FIREBASE_STORAGE_EMULATOR_HOST Environment Variable does not work with Admin SDK

Abierto
#874 5 comentarios 8 reacciones 1 asignado Reclamado por @jonathanedey Ver en GitHub
api: storage
Lenguaje dominante
Java
Estrellas
620
Forks
305
Merge medio
3 h 23 min
PR fusionados (30 d)
1

Descripción

#### My environment:

* Operating System version: Mac OS Sonoma 14.0 (23A344)
* Firebase Admin SDK version: 9.2.0
* Firebase Product: Storage Emulator

#### The problem:

When setting the environment variable "FIREBASE_STORAGE_EMULATOR_HOST" to 127.0.0.1:9199 (the default Storage Emulator Port and IP) to use the Firebase Storage Emulator the Admin SDK does not detect this environment variable.

Other Environment variables such as "FIREBASE_DATABASE_EMULATOR_HOST" and "FIRESTORE_EMULATOR_HOST" do work perfectly fine and as expected. They make a connection to emulators on the device.

I have gone as far to test and see if this issue is persistent on other Admin SDK's such as the Node.Js SDK. It is NOT an issue that persists on the SDK for Node.js.

As see here, this was previously an issue filed for the Firebase Admin SDKin the GO Repository for the Admin SDK ([see here)](https://github.com/firebase/firebase-admin-go/issues/520) and was fixed here [(see here)](https://github.com/firebase/firebase-admin-node/pull/1175) and has been since claimed to be fixed and the logic used in the Node Admin SDK project will be implemented.

The same issue previously on the Go Repo, appears to be present on the Admin Java SDK. Even using the "STORAGE_EMULATOR_HOST" environment variable as it was changed to in the GO repo, does not work.

Documentation on the Firebase Admin SDK [docs](https://firebase.google.com/docs/emulator-suite/connect_storage) is also incorrect if this is the case.

Screenshot 2023-11-03 at 5 32 06 PM

#### Steps to reproduce:

Set either environment variable "STORAGE_EMULATOR_HOST" or "FIREBASE_STORAGE_EMULATOR_HOST" to your Emulator host address and port (the default is 127.0.0.1:9199)

Use the Java Admin SDK to try and make a call like normal.

See it fail and use the production Cloud Storage instance.

#### Relevant Code:

Environment Variable Set via Intellij Run Configuration

Screenshot 2023-11-03 at 5 30 56 PM


InputStream input = this.getClass().getResourceAsStream("/service-account.json");
assert input != null;
GoogleCredentials googleCredentials = GoogleCredentials.fromStream(input);

FirebaseOptions options = FirebaseOptions.builder()
.setCredentials(googleCredentials)
.setProjectId("project-id")
.setDatabaseUrl("https://project-id-default-rtdb.firebaseio.com")
.setStorageBucket("project-id.appspot.com")
.build();

FirebaseApp.initializeApp(options);

InputStream fileInput = this.getClass().getResourceAsStream("/someFile.anyExtension");
Bucket bucket = StorageClient.getInstance().bucket();
bucket.create("someFile.anyExtension", fileInput, "application/anyExtension");

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.