Hello everyone,
Since two weeks, we have been having multiple intermittent build failures with the following error while trying to install Firebase CLI from firebase.tools.
#!/bin/bash --login -eo pipefail curl -sL firebase.tools | bash
Exited with code exit status 7
CircleCI received exit code 7
It’s worth sharing that re-running the build goes through without issues. So wanted to check if the team is aware of this or anyone has been facing this already.
Regards,
Have also raised a ticket with the firebase.tools team here
They suggested checking if there were any challenges accessing from CircleCI side making these connections to firebase.tools.
+1 getting that also on our circleci since around 2 weeks ago
but previously the exit code is 1 and got 443, now it returning exit 7
but previously the exit code is 1 and got 443, now it returning exit 7
Can confirm same behavior at our end as well. Good to know we are not alone.
+1 for this 
+1 for us too. Exactly the same issue. Kind of annoying. 
+1 been getting the same issue intermittently.
Exited with code exit status 28
CircleCI received exit code 28
-- Checking for existing firebase-tools on PATH...
-- Checking your machine type...
-- Downloading binary from https://firebase.tools/bin/macos/latest
curl: (28) Failed to connect to firebase.tools port 443 after 75009 ms: Operation timed out
-- Setting permissions on binary...
chmod: /usr/local/bin/firebase: No such file or directory
bash: line 255: /usr/local/bin/firebase: No such file or directory
Something went wrong, firebase has not been installed.
Please file a bug with your system information on Github.
https://github.com/firebase/firebase-tools/
-- All done!
Exited with code exit status 1
CircleCI received exit code 1
Can confirm the same issue from my end as well.
Hi!
Thank you for reporting the issue with the error.
I was able to replicate the issue and sent an internal message to the macOS team; asking if they made any changes to network recently.
While we investigate in this issue I would recommend using a workaround to install using npm and more details on the link below.
npm install -g firebase-tools
Update from me:
In our company, we’re able to solve the issue by using plugin gem 'fastlane-plugin-firebase_app_distribution' in our fastlane/Pluginfile (we’re using Fastlane anw), and remove the step for curl firebase-tools .. above
@revoreva Thanks for confirming! 
It looks like we had a mix of both approaches in our setup. We fixed this issue by only keeping the way of using the fastlane-plugin-firebase_app_distribution fastlane plugin instead of installing the firebase.tools directly via curl.
Hi!
I got an update from the macOS team and seems like the issues is only happening when using curl and it seems like using wget never fails. We are still continuing to investigate why using curl fails but as for a workaround I would recommend to try wget.
One note: wget is not pre installed so you would need to download with the command brew install wget which takes about a minute to download. We are working to add wget to be preinstalled.
- run: |
brew install wget
wget -S -O ./firebase_bin https://firebase.tools/bin/macos/latest
Thanks for the workaround!
Will use it till we hear back on why curl could be failing.
This worked perfectly for us.