Skip to main content

Firebase FAQ’s

Some common checks to perform:​

  • Check if you are running the firebase init and deploy commands in the correct directory.
  • Follow the quest steps properly.

1 . What should I do if I get “Error: Failed to create project. See firebase-debug.log for more info.", after you provide a projectID?

error

Solution:

  • See your firebase-debug.log file.

  • If the error is as shown in the image below(see the lines marked in red)

  • Ensure that your projectID contains only lowercase characters and starts with an alphabet.

  • If the error is as shown in the image below

    unnamed

  • Create your firebase project in the browser.

  • Visit https://console.firebase.google.com , then click add project and follow the steps to create the project.

  • In your terminal, choose the option ‘use existing project’ and continue.

2 . If you are running firebase commands using Windows powershell and encounter the error shown below.

powershell error

Solution:

Use the Command Prompt (cmd) or Git Bash to run those commands.

Solution:

In powershell, type the below(underlined) command and execute Set-ExecutionPolicy RemoteSigned -Scope CurrentUser. Then continue with the firebase commands.

3 . Upon visiting your deployed url, if you don’t see the intended page and instead see the page as shown in the image below.

webhosting

Solution:

  • It means that the index.html file in your public directory was overwritten with Firebase code. This happens if you chose Y in the CLI when the file was asked to be overwritten.

Solution :

  • Open your public directory's index.html file and replace the code in it with the code you want to deploy (in the case of quests, this means the code provided in quest steps), and also check the other files in the public directory, such as css and js files, to ensure they contain the code you want to deploy. Once the files in your public directory contain the correct code, proceed to redeploy using the "firebase deploy" command in your CLI.

4 . If you encounter the error "HTTP Error: 403, The caller does not have permission" in your firebase-debug.log file.

Solution: You may want to check if you are logged in on your terminal. The Suggested solution is to execute the following commands in your cli:

  • firebase logout
  • firebase login
    • and continue with further steps

Solution:

  • Create your firebase project in the browser.
    • Visit https://console.firebase.google.com , then click add project and follow the steps to create the project.
    • In your terminal, choose the option ‘use existing project’ and continue.

5 . 404: Page not found

404

Solution:

Project Name should be lowercase.

That's because when you were asked if you want to use your public directory, you choose NO instead of just pressing Enter. Start the step again from firebase init, and follow the steps from the campaign accordingly

Public folder shouldn’t override on deploy. Replace all files on the public folder and redeploy, but this time choose no

firebase deploy --only hosting

6 . Firebase queries mostly relate to Authentication and Terminals. Mostly Windows users experience these problems.

Solution:

  • It seems as if you have created a project once on Firebase through their website. Then, on Windows, you can create new projects using the CLI. It works fine.
  • So if people have previously created a Firebase demo project, they can either follow quest instructions for creating project via CLI or use the existing project option.

7 . CSS is not applying

Solution: The file name should not be the same as the index.html file.

If your css folder is in capitalized form:

  1. Rename it to lower case
  2. Save
  3. Redeploy