-
Notifications
You must be signed in to change notification settings - Fork 28
Description
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
Google Cloud Console warns to update node version:
Node.js 20 will be deprecated on 30 Apr 2026 and decommissioned on 30 Oct 2026. Please update to the latest runtime version available.
- manually update package.json node version and other cloud function data that is not available to edit/set in flutterflow
- Deploy cloud function via Flutterflow to update code
- code gets updated, but also reverts the package.json config
Expected Behavior
I would expect it to not overwrite settings that I cannot control in FlutterFlow.
Alternatively, allow to set node.js version and other missing config in the FlutterFlow cloud function UI.
I would also expect FlutterFlow to deploy new cloud functions with non-deprecated node version (eg 22) right away.
Steps to Reproduce
- Create a Cloud Function in FlutterFlow
- deploy via the FlutterFlow deploy button
- open v1 cloud functions page in google console
- click on the create cloud function with node warning
- change function to node.js 22
- open FlutterFlow again
- deploy again
→ Your Cloud Function got reverted to node 20.
Reproducible from Blank
- The steps to reproduce above start from a blank project.
Bug Report Code (Required)
ITESl8ncx5BgobQE1YfuY8dQhR4nHDM2a4NEk+pHdw0gIqL0PYwpWvT4QGBbQsjjfX5+AE38uFM0pODKi/D9A+4EHAyHbI8//5ZIbgyXLTimVKa2DKrgPHFCJ/1RGm6506urpBJNLvRaW1Fpig/GSw==
Visual documentation
warning in google cloud console: https://storage.googleapis.com/cassy/ShareX/cassy/2026/02/11/DOcqkBspja_03s_32m_17h_date_11_02_2026.png
Environment
- FlutterFlow version: v6.5.3 or latest in browser
- Platform: web and FlutterFlow app
- Browser name and version: latest firefox
- Operating system and version affected: windowsAdditional Information
This means I am no longer able to deploy cloud functions via FlutterFlow, without re-doing changes like node version upgrade every time I deploy.
Also means it's more difficult to track if the cloud function is up to date across different environments, since FlutterFlow won't warn.
Finally, an extra step to upgrade node version is required after deploying new function, when I would expect FlutterFlow not to create functions with deprecated config.