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
Failed to deploy to hosting with 'Failed to list functions for project' error #5071
Comments
debug log when it runned in Github Actions via FirebaseExtended/action-hosting-deploy https://github.com/FirebaseExtended/action-hosting-deploy
It is also occurred from local Mac. |
Same here. |
Same here.
I‘m not using cloud functions. |
+1, same error and not using cloud functions. Occuring with Github Actions, for deploying code on PR and on merge to Firebase Hosting. |
We face the same issue when trying to deploy to Firebase Hosting on a PR or on merge using GitHub actions. The logs include the lines:
|
If someone need to fix it asap, you can reproduce what i did on my org forked version appchoose/action-hosting-deploy@e63a636 and then use your own version waiting for a fix on firebase side. |
this worked for me as a quick workaround: |
Same here. @Klaitos solution worked perfectly 💪 |
a simple workaround for me is I tried to downgrade to the previous version npm uninstall -g firebase-tools and it works.. |
I notice others are seeing this when running |
Works for me too I have no functions on this project - it is a very simple static site and I didn't want to mess around with IAM creating permissions for something that doesn't exist I hope a fix will be out soon and I can upgrade again |
Awesome, this work for me too. Thank you. |
Thanks for raising. I'm taking a look. |
Alright - I got this narrowed down and the PR above should fix it. We'll get a build out today. |
Thanks for the support @bkendall! |
FYI- This regression broke several of our projects that I had set up with automatic github deploys using the https://firebase.google.com/docs/hosting/github-integration docs. While I had a suspicion that the latest firebase-tools release was the cause, there was no trivial way to revert to a working version, since the github action always uses the latest version (https://github.com/FirebaseExtended/action-hosting-deploy/blob/0f248036885ae672f78587669fa2923f0ef6cac2/src/deploy.ts#L79). And so our deploys have just been broken on multiple projects for 20+ hours. For comparison, we also use vercel for some of our projects, and it's never had a hiccup on this order of magnitude. I've opened FirebaseExtended/action-hosting-deploy#242 to suggest that the github action pins to a known-good version of firebase-tools, but I'm curious if it would be feasible / reasonable to add some CI checks and/or pre-release checklist steps to firebase-tools that just test that "firebase deploy" works fine on a vanilla free firebase project? Thank you kindly! |
Worked for me this, after updating deploy to hosting was broken |
@bkendall This error still happens on the latest version
The log on this comment #5072 (comment) should help assess what's going on. The error happens after the log |
@johnnyasantoss can you provide a new |
yep firebase deploy log
|
@johnnyasantoss workaround for "failed to list functions" for me was to create Service Account with these roles:
and use serviceaccount.json path in |
@bkendall it seems to have fixed the issue. Thanks! |
We ourselves have been using - name: 'Firebase deploy'
uses: 'FirebaseExtended/action-hosting-deploy@v0'
with:
repoToken: '...'
firebaseServiceAccount: '...'
projectId: '..'
channelId: live
entryPoint: ./...
firebaseToolsVersion: 'v11.13.0' # <--------------- Here Commit in question which added the support: <<<<<<<<< |
[REQUIRED] Environment info
firebase-tools: 11.14.0
Platform: macOS with M1 chip
[REQUIRED] Test case
I just updated firebase-tools from 11.13.0 to 11.14.0 and exec deploy command.
Then following error occurred.
[REQUIRED] Steps to reproduce
Same above.
[REQUIRED] Expected behavior
The deploy sequence will be completed.
[REQUIRED] Actual behavior
The error occurred.
Because I don't use cloud functions, I think this is a bug.
Thank you.
The text was updated successfully, but these errors were encountered: