Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

FIREBASE_STORAGE_EMULATOR_HOST Environment Variable does not work with Admin SDK

Ouverte
  • Quelque chose ne va pas ?
#874 5 commentaires 8 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

@jonathanedey y travaille déjà.

Depuis le 14/2/2025.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

api: storage
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) and was fixed here (see here) 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 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");
Langage dominant
Java
Étoiles
620
Forks
305
Merge moyen
4 j 9 h
PR mergées (30 j)
4

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de firebase/firebase-admin-java

Toutes les issues de firebase/firebase-admin-java

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.