⛔ Error: Unknown error. Please contact support@flutterflow.io.
Troubleshooting Checklist
Below follows a checklist that you can follow step by step to get the issue fixed. This is a collapsible step guide that has details on each. Make sure to expand the step if the previous step didn't fully resolve the issue.
1. Ensure firebase@flutterflow.io has all necessary permissions
Cloud function admin permission needs to be enabled for
firebase@flutterflow.ioIn your Firebase project.Additional Permission Like
editorandService account userneeds to be enabled.To add the permission, navigate to Project Settings> User and Permissions > Advanced Settings Permissions.
2. Make sure there are no errors in the custom code for cloud functions
Syntax errors can cause the deployment to fail. It is advised to cross-check the code before deploying.
This can be done locally on an IDE of your choice.
3. Make sure the project is on the Blaze plan on Firebase
If cloud functions cannot be deployed, be sure to confirm if the project is in Blaze plan and not Spark plan.
Additionally, cross-check the logs in the console log sometimes, GCP send the log back to inform you that the project is in the Spark plan.
In some cases in Firebase, the project might be showing a blaze, but in GCP, the billing failed. This should be another check to confirm if the billing is active or if it has expired.
4. Check if any other cloud function deployment succeeds (push notification, Stripe, etc.)
If you have other successfully deployed functions, this is an indication that Firebase configurations are properly set; what you need to check is now the configurations related to Cloud Functions and the actual code, if there are any errors or region misconfigurations.
5. Make sure the region is explicitly selected and is not left as [default] - on both advanced Firebase settings and in the cloud function deployment page
The region for the cloud function deployment should be set to the region that is set in your Firebase project settings.
The region should not be left as the default; this region should correspond with all deployed cloud functions in the project.
6. Different Cloud function protocols (HTTP VS Callable Functions)
Suppose you had deployed the cloud function as an HTTP function. In that case, if you try to redeploy the same function as a callable function, the deployment will still fail, and you will get this error .
[makeUserAdmin(us-central1)] Changing from an HTTPS function to a callable function is not allowed. Please delete your function and create a new one instead.
For this case, you will have to delete the cloud function in the Firebase Cloud function section and then modify the Function in FlutterFlow and re-deploy the function.
7. Ensure that the package.json file is not left blank and that it doesn’t have invalid characters
Ensure that you use the generated package.json file; don’t make any changes to the file unless you are adding packages.
In cases where FF fails to generate the file details, it is recommended to use this
{
"name": "functions",
"description": "Firebase Custom Cloud Functions",
"engines": {
"node": "18"
},
"main": "index.js",
"dependencies": {
"firebase-admin": "^11.8.0",
"firebase-functions": "^4.3.1"
},
"private": true
}
8. Ensure/cross-check that the version of the third-party library used is valid
It's normal to forget to include third-party packages used in the cloud function in the package.json file. For instance, if you are using axios, please ensure that the package is already included in the package.json file.
9. Ensure that you have deployed Firebase rules sometimes. This can block cloud function deployments
Lastly, ensure that you have deployed your Firebase configuration settings from FlutterFlow. This includes Firestore rules and Firestore indexes.
These can block cloud function deployment when they are still not deployed.
Additional Resources
Other Community Article