FAQ and troubleshooting

This page provides answers to frequently asked questions (FAQs) about App Hosting.

App Hosting provides preconfigured build and deploy support for Next.js and Angular, where we've committed to understanding those frameworks and interpreting their native configurations. For any Node.js application with a build and start script, App Hosting will attempt builds, but cannot dependably guarantee success. See Framework integration.

The regions for App Hosting are likely to expand over time. See App Hosting locations for the most up-to-date information.

Currently you can't, but support for other providers is in the long term roadmap for App Hosting.

If your repository does not appear in the list of options when you are creating a new backend in the Firebase console, first try selecting Refresh list. If the preferred repository is still not available, you may need to add it using the option to Grant access to a new repository in GitHub.

Additionally, you can manage repositories with the Firebase App Hosting GitHub application. To do this, go to your GitHub profile, and select Settings and then Applications. In the table row for the Firebase App Hosting application, click Configure to manage repositories.

Currently, changing the repository isn't possible. However, you can create a new backend associated with the preferred repository within the same project, or create a new backend in a separate project.

Headers are framework-dependent. Do whatever you would normally do for your framework.

Yes, you can perform local tests of your app prior to App Hosting deployment using the App Hosting emulator, which is part of the Firebase Local Emulator Suite. See Locally test your app deployment .

In such cases, it's possible that your error may have come from Cloud Run. Check the status of the rollout to be sure.

Currently, it is not possible to change or remove the GitHub account linked to a Firebase project. To use a different GitHub account, create a new backend within the same project or create a new backend in a separate project.

Though it was not available at the launch of the App Hosting preview, the Set-Cookie HTTP response header now works as expected.