Publishing problem encountered by a newbie.

App Hosting
1

I completed my first project using Firebase Studio today, and an error occurred during deployment. “Failed to create project”. No specific reason for creation failure was found. Ask for help. Thank you, boss.When encountering such a creation failure, what methods should I use to troubleshoot the problem.

2

I am also encountering the same problem despite having only one active project. I am unable to publish other projects. That is what I am encountering. Kindly anyone assist.

image
image1366×768 207 KB

3

You need to have a billing account and upgrade to a blaze account. If you already have that setup I’ve found Firebase isn’t happy if you’re logged into different Google accounts in the browser. Log out of other accounts and only have your Firebase account logged in.

4

I actuallly have a billing account on blaze plan. I also dont have multiple emails

5

Have you tried connecting your account in Firebase project setup? Or you coild try Firebase deploy from the terminal. Next time I’m logged in I’ll check and share the steps. Similar to you have have issues deploying from the publish button so ended up with a couple of work arounds

6

Kindly do so. I will appreciate

7

There was an unknown error while provisioning your cloud resources. This error baffles me for sure.

8

Hi. I’ve not been able to use my billing account to test my Workaround however I might have found my issue that could be similar to yours?

I noticed in cloud billing ALL my previous Firebase projects, even ones I thought I had removed, are still listed. I get an error in billing that I have reached my project limit so I can’t use blaze plan unless I increase the project limit or remove some projects.

9

Hi — I’m not sure whether your publishing problem has already been resolved, but in case you’re still stuck, here’s a methodical approach that tends to resolve many common deployment issues. Feel free to tell us your current status (resolved / still failing / stuck at build, etc.), and I’ll help you further from there.

:toolbox: Common Publishing Issues & Recovery Steps

  1. Check Build Logs & Errors

    • When you run your publishing (firebase deploy or through the tool UI), note any error messages or stack traces.

    • Common failure points: missing environment variables-a known suspect to my projects:upside_down_face: , build script errors, Node version mismatch.

  2. Verify firebase.json & hosting Configuration

    • Make sure your firebase.json has the correct "public", "rewrites", or "cleanUrls" settings.

    • Example:

      {
  "hosting": {
    "public": "build",
    "ignore": ["firebase.json", "**/.*", "**/node_modules/**"],
    "rewrites": [
      { "source": "**", "destination": "/index.html" }
    ]
  }
}

  3. Ensure Build Output Directory Aligns

    • Sometimes the build script outputs to dist/ or build/, but firebase is set to serve another folder. Try checking here if the above doesn’t move things along.

    • Confirm that your build step (e.g. npm run build) produces the folder name matching the public in firebase.json.

  4. Check Node / Tooling Versions

    • If you’re using features (ES Modules, optional chaining, etc.), your build pipeline (webpack, Babel, or TS) must support them.

    • Make sure local versions (Node, npm, dev deps) match what your publishing environment expects.

  5. Test Locally Before Deploying

    • Locally serve your build folder via a simple HTTP server to see if it works before deploying:

      npx serve build

    • If it fails locally, the error is in your build—not firebase deployment.

  6. Use Fallback / Rollback Plan

    • If your last published version worked, consider rolling back to that as a checkpoint.

    • Deploy small, incremental changes rather than large ones, so you can isolate where publishing fails.

If you still have the project open, you can paste the exact error message or build logs into the thread here — I’d be happy to take a look and help you pinpoint the approach to resolving.

Here is a sample from one of my projects: /
├── .env
├── README.md
├── apphosting.yaml
├── components.json
├── next.config.ts
├── package.json
├── tailwind.config.ts
├── tsconfig.json
│
└── src/
├── ai/
│ ├── dev.ts
│ ├── genkit.ts
│ └── flows/
│ ├── generate-faction-lore.ts
│ └── smart-golem-upgrades.ts
│
├── app/
│ ├── actions.ts
│ ├── globals.css
│ ├── layout.tsx
│ ├── page.tsx
│ ├── dashboard/
│ │ └── page.tsx
│ ├── game/
│ │ └── page.tsx
│ └── mint-lab/
│ └── page.tsx
│
├── components/
│ ├── dashboard/
│ │ ├── dashboard.tsx
│ │ ├── event-feed.tsx
│ │ ├── faction-hub.tsx
│ │ ├── golem-forge.tsx
│ │ └── stats-overview.tsx
│ │
│ ├── game/
│ │ └── game-header.tsx
│ │
│ ├── landing/
│ │ └── coliseum-entry.tsx
│ │
│ └── ui/
│ ├── accordion.tsx
│ ├── alert-dialog.tsx
│ ├── alert.tsx
│ ├── avatar.tsx
│ ├── badge.tsx
│ ├── button.tsx
│ ├── calendar.tsx
│ ├── card.tsx
│ ├── carousel.tsx
│ ├── chart.tsx
│ ├── checkbox.tsx
│ ├── collapsible.tsx
│ ├── dialog.tsx
│ ├── dropdown-menu.tsx
│ ├── form.tsx
│ ├── input.tsx
│ ├── label.tsx
│ ├── menubar.tsx
│ ├── popover.tsx
│ ├── progress.tsx
│ ├── radio-group.tsx
│ ├── scroll-area.tsx
│ ├── select.tsx
│ ├── separator.tsx
│ ├── sheet.tsx
│ ├── sidebar.tsx
│ ├── skeleton.tsx
│ ├── slider.tsx
│ ├── switch.tsx
│ ├── table.tsx
│ ├── tabs.tsx
│ ├── textarea.tsx
│ ├── toast.tsx
│ └── toaster.tsx
│
├── hooks/
│ ├── use-mobile.tsx
│ └── use-toast.ts
│
└── lib/
├── mock-data.ts
├── placeholder-images.json
├── placeholder-images.ts
├── types.ts
├── utils.ts
└── wallet.ts.

Use this to check against or as a template for what a clean dev hierarchy looks like. If you haven’t done this yet, try using Figma first, then StackBlitz; combine with reading the Documentation for 72 hrs. and checking to see if your project is Rules Compliant. If you are using Code Snippets, use caution as it warns. You can create silent errors that will pass inspectors, only to surface later when you are really deep in development. Make sure you have a clean, stable Git Repository that matches your projects /src Tree