I'm just looking into firebase, after logging in with my google account and creating a project I cannot create a real-time database in the dashboard/console, the database permission dialog appears and clicking ok give a 500 error in the console.
health check says the service is up, and no detail error information is available is there another way to do this, maybe a cli tool or legacy dashboard that still works?
firebaser here
There was a problem with creating Firestore and Realtime Databases on newly created Firebase projects for the past few hours. Existing projects and databases were not affected, and no data was lost.
The problem has been solved now.
Related
I'm working on a product which uses Firebase as its backend. Since firebase exposes the API keys to the user so that could be a security issue. So, after doing some research I've set the database security rules along with API keys restrictions.
But, now I'm unable to use it in local development as well. I was thinking of creating another firebase project and use that as a testing environment and use the existing one as production.
Since the existing project has a lot of data and users. I want everything similar in the new firebase project as well. But I'm unable to find an efficient way to do so. Can anyone please suggest what would be the best option here? Should I create a new testing environment or is there a way to allow me to use the keys locally without it causing a security concern?
Any help would be great. Thank you for your time.
There is no specific command to replicate one project to another, but you can build the necessary functionality yourself with each product's APIs.
For porting users between projects you can use:
The Firebase CLI, which has auth:import and auth:export commands.
The Firebase Admin SDK, which has commands to list all users and import a list of users.
For transferring data between the projects, you can use the API of the relevant database to read/write the data.
I have gone through many of the Fabric and Firebase documentation to see what will happen to my production Android app, if I do not migrate or change the Fabric sdk.
If I don't do this, what will be the impact to my app, my users, myself (What Crash information won't I be able to see)
To be more specific:
Will the app be removed from the Play Store (Like what has happened for permission changes - I think this is not a serious problem and the app will not be removed)?
The app will not report any crash logs in Fabric
Is there a way to see the crash logs in Firebase without updating the app?
Any other changes I need to know about?
Kevin from Fabric here!
To answer your questions:
We haven't run into anyone having their app removed for permissions reasons after completing the migration - this shouldn't be an issue.
After setting up the migration, you will be able to see your Crashlytics information flowing to both your Fabric and Firebase dashboards without any further set up required.
The steps are:
-Make sure you're an admin in Fabric and have the "Owner" role in Firebase
-Head to https://fabric.io/firebase_migration
-Drag the desired Fabric apps to their locations in Firebase
-The apps will be linked and crashes will be viewable in both
As long as you continue to update the Crashlytics dependencies as normal you shouldn't see any disruptions to your crash logs in either dashboard as of now.
Check out our roadmap to learn more about migration plans feature rollout.
I have a project for both Android and iOS that's using cloud functions for same app behavior and consistent data storing. For now we were debugging apps on single database, storage and authentication.
The problem is when I switch to release variant I want functions to operate on release database, storage and auth.
I've been searching for an answer to my problem and all I've found was this: How to access multiple Realtime Database instances in Cloud Functions for Firebase
but it doesn't help too much.
Is there a way to go about that without making another Firebase project for release variant?
Ok, so basically just a while after posting this question I've found official firebase guide that helped me resolve this issue.
Short answer: no, you have to create another project in Firebase as described in guide.
After having issues with crashes in Android O and also seeing that GCM is fully deprecated we are trying to migrate to FCM. Keep in mind I did zero of the setup on this project, so I'm just trying to follow the migration guide. Our server side team is very busy right now, so I'm trying to make it as easy as I can for them.
So someone gave me owner permissions on the Google APIs dashboard for the project, where I can see that Google Cloud Messaging is enabled. So I gave owner permissions to an account we now use for all of our mobile online accounts and consoles.
Then I logged into the Firebase console, but when I click "add project" I do not have the option to import the existing GCM project, as the docs seem to say I should. It also doesn't show up for my personal work account either, even though it is also an "owner" account. I was really hoping to migrate this way so that we might not have to get new api keys.
However, I do see in the Google APIs dashboard that I can "enable" FCM from there. Will this create the Firebase project for me and if so will it generate new keys or can we use the old ones?
OR is it actually better to just create an entirely new FCM project?
I have an administrative panel that lists all users on my system. I would like to be able to delete the account of a saved user in firebase.auth().
I know the firebase provides an SDK for this, but I do not have a server on Node, my site is hosted directly on Firebase hosting.
Is there any other way to do this?
Create a Cloud Function (serverless) that deletes users using the Node.js Admin SDK. Then you can hit that endpoint whenever you want to delete a user: https://firebase.google.com/docs/hosting/functions
You do have a node server. It's free. You can install node on your laptop or even better you can stand one up online. I use the free tier of cloud9 IDE (I do not work for them and I'm not trying to sell anything).
Easiest of all, use Firebase's web console to delete a user, unless you have a need to build out a more elaborate system.