Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

firebase emulators:exec failing in 9.16.1, 9.16.2, 9.16.3 and 9.16.4 #3681

Closed
delucis opened this issue Aug 13, 2021 · 0 comments · Fixed by #3684
Closed

firebase emulators:exec failing in 9.16.1, 9.16.2, 9.16.3 and 9.16.4 #3681

delucis opened this issue Aug 13, 2021 · 0 comments · Fixed by #3684

Comments

@delucis
Copy link

delucis commented Aug 13, 2021

Environment info

firebase-tools: 9.16.4

Platform: Ubuntu

Test case

I have a test suite running in CI using firebase-tools. Here’s the command:
firebase emulators:exec --only firestore 'npm run jest'.

These tests ran and passed with firebase-tools 9.16.0 (and earlier) (most recent successful run).

When upgrading to 9.16.2 or 9.16.4, the CI fails with a “No currently active project” error. Here’s the error in the PR attempting to upgrade to 9.16.4.

My guess is that #3636 is the culprit.

Steps to reproduce

  1. Upgrade firebase-tools to a version greater than 9.16.0
  2. Run a command with firebase emulators:exec

Expected behavior

The command continues to run as with <=9.16.0

Actual behavior

The command fails with the following error:

Error: No currently active project.
To run this command, you need to specify a project. You have two options:
- Run this command with --project <alias_or_project_id>.
- Set an active project by running firebase use --add, then rerun this command.
To list all the Firebase projects to which you have access, run firebase projects:list.
To learn about active projects for the CLI, visit firebase.google.com/docs/cli#project_aliases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant