I am new to Firebase. When I am creating a new Firestore database am getting this error
Enabling Cloud Firestore will prevent you from using Cloud Datastore with this project, notably from the associated App Engine app
All solutions I found online are completely targeting experts/individual who knows their way around Firebase and Google Cloud. To me, this error is a roadblock. I tried using my other Gmail accounts, creating new projects and the same error appears. even the cancel and close buttons seen are not working I have to refresh just to get back.
Kindly help or guide me what should I do.
Based on #JoshL.Minga and #RenaudTarnec comments, the issue was narrowed down to a specific browser. After switching to Safari it didn't reproduce.
This issue has been reported to Google support.
Aside from that, you may want to try creating a Frirestore DB using a brand new project. Make sure that your new project is created via the Firebase console and not in the GCP console.
Related
Probably silly question, but is it possible to send errors using Crashlytics from users that downloaded my app from Google Play? Until now I was using Crashlytics to collect errors from my app distributed by Firebase (so it was only for me and invited people). But I have released my app on Google Play and I can't see any errors from devices that downloaded my app in Google Play. I read that when I link my Google app with Firebase I can see purchase and subscription and analytics but no mention of Crashlytics. So my question is.. Is it even possible? Thank you very much.
Is the package name the same on your "release" version on the store? If your test one was called com.patrik.coolapp.debug (which is the default if you're using a debug build) then you'll need to add com.patrik.coolapp as an App in your Project in the Firebase console.
If you already had Crashlytics set up (all the dependencies, added the plugin, FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true) somewhere in your app) then it should just work - here's some advice on testing:
https://firebase.google.com/docs/crashlytics/test-implementation?platform=android
So I finally made it..
I'd like to thanks to #cactustictacs for help.
The problem was that I did not integrate Google Play in project settings in Firebase, although it is saying that it is just for Analytics and Subscription.
Before I integrated Google Play in Firebase I tried to add FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true) .. it did not work, but I believe it could be usefull to someone.
It wouldn't be such a problem, but it is required to have Owner or Admin permissions on both Firebase account and Google Play console account (which I did not have). After I get the permissions, integration was enabled and I could see test crashes in Crashlytics.
I have created a Cloud Firestore Database and have it in Test Mode which means the read and write rules are pretty open for the next 3 weeks.
However when I try to add collections or documents from the web interface they do not show up on the database. I was able to add collections and documents from my android app but even those when I try to view I get "Error loading Documents".
I have tried Firefox and Chrome to see if it was a browser issue and I have disabled my Antivirus (avast) as well to see if that was the issue but no success.
What could be the problem?
There is no way to debug or answer this, you require backend assistance: I suggest reporting the problem to Firebase support. but most likely by the time you get a response, the server will fix itself.
https://firebase.google.com/support/troubleshooter/contact
I have a React Native app with Firebase crashlytics integrated. I am forcefully crashing the app by calling function which does not exist. (this.test()).
I am getting logs in crashlytics, but looking at that logs I am not able to track the exact issue location.
Logs are quite generic and which is not helping me to pinpoint the issue.
Is there any way to get more info on that issue from logs? or anything I need to do so that I can get the issue location? if we are getting an issue in the inded.js file can we trace back the exact js file in app which is causing the issue.
Please help me with this information. Than you for helping.
Firebaser here - it sounds like you'd benefit from Crashlytics custom logging. This tool allows you to log any messages you want that get appended to the Crashlytics crash report that gets sent up to the console. I'm not sure how the React Native wrapper for Firebase Crashlytics works or if it allows you to do this, but according to the React Native Firebase reference doc you should be able to.
With this tool, you could call log in your code whenever you want to record information about the session, the user, or whatever's happening with code that you're executing in the background.
I recently disabled App Engine in my project as I don't need it anymore. However, I am now greeted by the following when accessing Firestore in the Firebase console:
The problem is that App Engine is pretty costly (min $50/month)
I'd like to know if there is a way to use Firestore without paying this much.
Thanks
Update:
You can have app engine enabled for free, but I couldn't get it done for the following reason:
I had in my config (app.yaml) min_num_instances: 1. I haven't realised this and whenever I wanted to delete an instance I never could (with no error message: it just did not delete it without displaying anything)
It is not possible to use Firestore without having App Engine enabled.
I use Firestore in many of my apps however without ever paying for App Engine. Since App Engine is pay-as-you-use, there is no payment required until you use it.
Im trying to locate the link that is supposed to be created along with my app on Firebase(according to the udacity Firebase course).
I found many links but none of them were accepted by the "after lesson quiz" on udacity.
The content that they have is according to the old UI of Firebase so i cant follow it step by step.
Unfortunately that course is for Firebase 2.x (www.firebase.com) and is out of date. In the legacy Firebase docs, under step 5 : Read & Write to your Firebase Database, you can see that creating a Firebase reference required the actual web address for you app. This is no longer true.
The new and correct way to setup your Firebase app does not require you to use this web address. The steps for setting up a Firebase app now are HERE.