Known Issues
Build images left after deployment
Issue:
During deployment there is an error in log:
⠼ Deploying Firebase functions...⚠ functions: Unhandled error cleaning up build images. This could result in a small monthly bill if not corrected. You can attempt to delete these images by redeploying or you can delete them manually at https://console.cloud.google.com/gcr/images/your-firebase-project/us/gcfSolution:
Manually delete the images at the provided link. This is a known issue with Firebase CLI.
Some functions failed to deploy
Issue:
During first install some APIs are still being enabled causing some functions fail to deploy. During deployment there is an error in log:
Failed to create function projects/your-firebase-project/locations/us-central1/functions/payments-onPaymentUpdatedSolution:
Rerun the installer. The APIs should be enabled by now and the functions should deploy successfully. Check logs for any other errors.
Google Play Android Developer API error during purchases
Issue:
During Android purchases, the following error occurs:
code":403,"message":"Google Play Android Developer API has not been used in project 12345678901 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/androidpublisher.googleapis.com/overview?project=12345678901 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.Solution:
Visit link provided in the error message and enable the Android Publishing API. Wait a few minutes and try again.
Non-default Firebase Functions region deployment location causes errors
Issue:
You set CLOUD_FUNCTIONS_LOCATION variable which is responsible for a Firebase Cloud Function deployment region other than the default us-central1. The client-side Firebase Functions call is not updated accordingly.
Solution:
Please update the Firebase Functions call accordingly. For more information, see Firebase Functions regions.
Unable to login with email + password
Issue:
You are unable to login with email + password, but other authentication methods work fine.
Solution:
Disable Email Enumeration protection. If you are going to use FirebaseUI for authentication screens in iOS, Android or Web , you need to disable Email Enumeration protection. Otherwise, the FirebaseUI will not work correctly until Google resolve this GitHub issue. In our example apps, we use FirebaseUI for authentication.