> Documentation index: https://firebase.google.com/docs/app-hosting/llms.txt

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

## App Hosting FAQ

#### Does App Hosting support frameworks other than Next.js and Angular?


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 a number of
[other frameworks](https://firebase.google.com/docs/app-hosting/frameworks-tooling.md.txt#community-supported-frameworks),
the developer community supports App Hosting
framework adapters. Additionally, for any Node.js
application with a build and start script, App Hosting
will attempt builds, but can't dependably guarantee success. See
[Framework integration](https://firebase.google.com/docs/app-hosting/about-app-hosting.md.txt#frameworks).

#### Which regions does Firebase App Hosting support?


The regions for App Hosting are likely to expand over time. See
[App Hosting locations](https://firebase.google.com/docs/app-hosting/about-app-hosting.md.txt#locations)
for the most up-to-date information.

#### Can I use GitLab or other Git providers besides GitHub for deployments?


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

#### Why can't I find my repository in the Firebase console UI?


If your repository doesn't 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.

#### Why won't my site display normally in Android mobile app WebView?


Apps that configured a custom domain with the Firebase console prior to
Q3 2025 may find that the site doesn't display properly in Android WebView.
This occurs because CNAME records used during that period were not
compatible with Android WebView.


To resolve this issue, remove the custom domain from the App Hosting
backend and re-add it. The updated console UI provides three new records:
an A record and a TXT record for the domain, and a CNAME record for the
ACME challenge subdomain for certificates. Use these records in place of
the previous CNAME record.

#### How do I change the repository associated with my App Hosting project?


In the Firebase console, open your App Hosting backend and go to
**Settings \> Deployment** . From the
**GitHub repository** section, you can disconnect the current
repository or select a different repository connected to your project.

#### How can I set headers for my App Hosting site?


Headers are framework-dependent. Configure headers according to your
framework's documentation.

#### Is there an emulator for local development with App Hosting?


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](https://firebase.google.com/docs/app-hosting/emulate.md.txt).

#### Why do I see errors in App Hosting but not in Cloud Build?


Your error might come from Cloud Run. Check the rollout status to make
sure.

#### How do I change or remove a linked GitHub account?


To remove the linked GitHub account, open
[Developer Connect](https://console.cloud.google.com/developer-connect/connections),
ensure your project is selected, and delete the
`firebase-app-hosting-github-oauth` connection and the connection
that starts with `apphosting-github-conn-`. When you open
App Hosting in the Firebase console, you should now be able to set
up a new GitHub connection.

#### How can I set cookies for my App Hosting site?


Though it wasn't available at the launch of the App Hosting preview,
the `Set-Cookie` HTTP response header now works as expected.

## General App Hosting limitations and troubleshooting

- Due to an
  [issue in Cloud Run infrastructure](https://docs.cloud.google.com/run/docs/known-issues#deployment-latency),
  creating or updating resources might be slower than expected in some
  regions like `us-central1`. If deployment latency is an issue in a
  particular region, Google recommends deploying to another region.

- The CDN for App Hosting can only include a specific set of request
  headers in its cache keys. This list includes:

  - Next.js headers: `RSC`, `Next-Router-State-Tree`,
    `Next-Router-Prefetch`, `Next-Router-Segment-Prefetch`, and `Next-Url`.

  - Cloud CDN standard headers: `Accept`, `Accept-Encoding`,
    `Access-Control-Request-Headers`, `Access-Control-Request-Method`,
    `Origin`, `Sec-Fetch-Dest`, `Sec-Fetch-Mode`, `Sec-Fetch-Site`,
    `X-Goog-Allowed-Resources`, and `X-Origin`.

  Note that if a response contains a `Vary` header with a value not listed
  here, then the CDN won't cache it.
- Uncached static files are served out of Cloud Run; in a later
  release, they'll be stored and served from the App Hosting origin for
  better performance.

- The Firebase console may intermittently show a "build was not found and
  is invalid" error on backend creation.

- All backends in the same project share a GitHub org/account. They can be
  connected to different repositories under that org/account. To create
  backends that are connected to different GitHub accounts, put them in
  separate projects.

## Angular app limitations and troubleshooting

Though App Hosting support for Angular is actively in development and
expanding, it has the following limitations:

- **I18n**: While core I18n functionality works, direct navigation to SSR pages can result in errors.
- **Localization**: Building versions for different locales isn't supported.
- **Builders**: Only the Application builder is currently supported.
- **Environments and Monorepo Tooling**: Angular projects that have more than a single application target will fail. For more complete monorepo support, use Nx.

### HTTP 400 Errors and Proxy Trust in Angular SSR

If your Angular application deployed on Firebase App Hosting encounters
HTTP 400 (Bad Request) errors, host validation blockers, or proxy trust
failures, follow the recommended solution for your Angular version:

- **Angular v19, v20, and v21** : You have two ways to resolve these HTTP 400 errors:
  - Upgrade dependencies: Run `npm update @angular/core @angular/ssr` to install the latest patch release for your current Angular version.
  - Manual configuration: Apply a code-level configuration fallback by setting `trustProxyHeaders: true` in your server configuration (see [Configuring trusted proxy headers](https://angular.dev/best-practices/security#configuring-trusted-proxy-headers) in the Angular documentation).
- **Angular v22**: The first build on a new backend might return 400 errors. To resolve the issue, generate a second build. All subsequent builds should work as intended.

## Next.js limitations and troubleshooting

- By default, the [built-in NextJS image optimization](https://nextjs.org/docs/app/building-your-application/optimizing/images) is disabled on App Hosting unless you explicitly set [`images.unoptimized`](https://nextjs.org/docs/pages/api-reference/components/image#unoptimized) to false or use a custom [Image Loader.](https://nextjs.org/docs/app/api-reference/config/next-config-js/images#example-loader-configuration) See [Optimize image loading on
  Next.js](https://firebase.google.com/docs/app-hosting/optimize-image-loading).
- By default, Next.js writes cached pages and data to the file system, which counts toward the memory of each serving instance on App Hosting. If your instances restart with `Memory limit exceeded` errors, see [Configure
  server caching on Next.js](https://firebase.google.com/docs/app-hosting/configure-server-caching).
- Currently, App Hosting limits the caching for NextJS apps using [middleware](https://nextjs.org/docs/app/building-your-application/routing/middleware). Over time, cache hit rates should improve.
- URL paths containing percent-encoded characters are decoded by Cloud Run. This may cause issues with features that expect only encoded URL paths, such as [Next.js parallel routing](https://nextjs.org/docs/app/building-your-application/routing/parallel-routes).