Deployment of firebase rules fails with an unexpected error
See original GitHub issueBug, feature request, or proposal:
When trying to run npx yarn run deploy
in /firebase/functions
the command fails with an unexpected error.
What is the expected behavior?
The deployment should work 😃
What is the current behavior?
i database: checking rules syntax...
✔ database: rules syntax for database machinelabs-b191b is valid
i storage: checking rules/storage.rules for compilation errors...
✔ storage: rules file rules/storage.rules compiled successfully
i functions: ensuring necessary APIs are enabled...
✔ functions: all necessary APIs are enabled
i storage: uploading rules rules/storage.rules...
i functions: preparing functions/dist directory for uploading...
i functions: packaged functions/dist (45.9 KB) for uploading
Error: An unexpected error has occurred.
error An unexpected error occurred: "Command failed.
Exit code: 2
Command: sh
Arguments: -c npm run build && firebase deploy && npm run clean_dist
Directory: /Users/pascal/Repositories/machinelabs/firebase/functions
Output:
".
yarn-log:
Error: Command failed.
Exit code: 2
Command: sh
Arguments: -c npm run build && firebase deploy && npm run clean_dist
Directory: /Users/pascal/Repositories/machinelabs/firebase/functions
Output:
at ProcessTermError.MessageError (/Users/pascal/Repositories/machinelabs/firebase/functions/node_modules/yarn/lib/cli.js:186:110)
at new ProcessTermError (/Users/pascal/Repositories/machinelabs/firebase/functions/node_modules/yarn/lib/cli.js:226:113)
at ChildProcess.<anonymous> (/Users/pascal/Repositories/machinelabs/firebase/functions/node_modules/yarn/lib/cli.js:30281:17)
at ChildProcess.emit (events.js:127:13)
at maybeClose (internal/child_process.js:933:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
What are the steps to reproduce?
Follow every step in the developer guide up the the section for #### Deploying Firebase rules and functions
What is the use-case or motivation for changing an existing behavior?
Which version of MachineLabs (or the package) is affected ?
latest on master
Is there anything else we should know?
Please execute the following commands in your terminal and post the output here
xterm-256color iTerm.app 3.1.5 /usr/local/bin/fish
v9.6.1
firebase --version:
3.17.7
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Unexpected error while deploying database rules
Firebase Error: Unexpected error while deploying database rules · This error usually means that you have a typo in the name of your...
Read more >Firebase CLI : Error: An unexpected error has occurred. #227
Tried 3 times. Always the same. Installed the firebase tools new with npm. Again the same error. Any help ?
Read more >An unexpected error has occurred.” while deploying firebase ...
I am trying to deploy a firebase function for my Android application. ... the deploy command I get an error that says “Error:...
Read more >Manage and deploy Firebase Security Rules - Google
Manage and deploy Firebase Security Rules ; Use the Firebase CLI. Generate a configuration file; Edit and update your rules; Test your updates...
Read more >Fix error ERR_INVALID_ARG_TYPE deploying to Firebase ...
You can find additional details about the error in the file firebase-debug.log in your project folder. In my case it contained the following ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yay, happy it works for you now! Keep us posted now how it goes.
As always: some good issues to start with are here: https://github.com/machinelabs/machinelabs/issues?q=is%3Aissue+is%3Aopen+label%3A"hotlist%3A+community-help"
Verified. It works! Going to close the issue.