Private API deployment fails with "must be on Blaze plan" error despite confirmed Blaze plan (same as #6655)

[sipaesgrupo-s021]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When attempting to deploy a Private API Call as a Cloud Function, FlutterFlow shows:
"Your Firebase project must be on the Blaze plan in order to deploy functions. Please upgrade your plan and try deploying again."

The connected Firebase project (sipaespay-app) is CONFIRMED on the Blaze plan — verified directly in Firebase Console (Usage and Billing page shows "Blaze" tag, project overview shows "Plan Blaze" badge).

This is the same issue as #6655, which was closed by mistake by the original reporter and never actually resolved.

Expected Behavior

Steps to Reproduce

1. Connect a Firebase project (sipaespay-app) that is already on the Blaze plan (confirmed in Firebase Console)
2. Go to an API Call configuration (e.g. "procesarticketentrada")
3. Enable "Make Private" under Advanced Settings
4. Save the API call
5. Click "Deploy APIs"
6. Observe deployment fails with "Not Deployed (Error)"
7. Click the info icon next to the error - it shows "Your Firebase project must be on the Blaze plan..."
8. Waited 8+ hours and retried - same error persists

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4ghcrqy5d2rsBE17r+LO9Vp2IUJno4bJc0sNobbxAjIoDoPJkUacz8VBBtXdend1VlKEWLkkIDw+DekvDlOO1eCxSBfYtyzqVQeBXzQnK/aovRO6mKe3xtMJpVBUjA06angiVSKrF2SWQcwzumJe+8cBPrK5P7Zwh9f6PHaOI=

Visual documentation

See attached screenshots showing: (1) Firebase Console confirming Blaze plan active, (2) FlutterFlow error message "must be on Blaze plan", (3) related issue #6655 with identical error.

Environment

- FlutterFlow version: (check via Help menu > About, or leave as "latest as of Aug 2026")
- Platform: Web
- Browser name and version (web): Chrome (latest)
- Operating system and version affected: Windows

Additional Information

This is blocking a critical security fix - we need to move a hardcoded API credential (Supabase key) out of a public API call header into a private Cloud Function, but cannot do so due to this bug. This matches issue #6655 exactly, which was closed by mistake by the original reporter and never resolved.

[Alezanello]

Hello!

For issues like this, please contact Support directly via the in-app chat. This GitHub issue repository is intended for issues that are not specific to an individual project.

Thanks!

[sipaesgrupo-s021]

Subject: Follow-up with no response - GitHub Issue #7388 (Blaze plan / Private API deployment) Hello FlutterFlow team, I'm writing because I opened a conversation in the in-app support chat almost an hour ago, but it automatically closed ("Your conversation has ended") without anyone viewing or responding to it. I'm sending the same content here by email as a backup. The GitHub Issues team (Ale Zanello) redirected me to this channel because my problem is specific to my account/project. Original issue reference: #7388 (This is the same problem reported in issue #6655) ────────────────────── ISSUE: ────────────────────── When trying to deploy a private API/Cloud Function, I receive the error "must be on Blaze plan" — despite having a confirmed and active Blaze plan on my Firebase account. ────────────────────── PROJECT DETAILS: ────────────────────── - Project: SipaesPay (ID: sipaes-pay-i6ijpx) - Firebase project: sipaespay-app (Blaze plan, active) - Affected function: procesarticketentrada - Account: ***@***.*** ────────────────────── CURRENT WORKAROUND: ────────────────────── For now I have this function set with "Make Private" = OFF as a temporary workaround, but I need to be able to deploy it as private for production. Could you please review my account and confirm whether there's a syncing issue between the Firebase Blaze plan and how FlutterFlow recognizes the plan? Thank you in advance. El jue, 13 ago 2026 a las 20:08, Ale Zanello ***@***.***>) escribió:

…

*Alezanello* left a comment (FlutterFlow/flutterflow-issues#7388) <#7388 (comment)> Hello! For issues like this, please contact Support directly via the in-app chat. This GitHub issue repository is intended for issues that are not specific to an individual project. Thanks! — Reply to this email directly, view it on GitHub <#7388?email_source=notifications&email_token=CLPCQ65Q2USRNVOPX5H6UZT5JX727A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRYGQ2TOMZYGY2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5284573864>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CLPCQ63ANIUPUOYRUFHPRBD5JX727AVCNFSNUABFKJSXA33TNF2G64TZHM2TENZQG4ZTQNJWHNEXG43VMU5TKMJUGA3TSNZXGUY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CLPCQ63JV3SUAN5S6JOLRLT5JX727A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRYGQ2TOMZYGY2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CLPCQ62ZYVFR7O3YA5ETXVT5JX727A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRYGQ2TOMZYGY2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>