Can't add anything to Cloud Firestore from console - firebase

I've searched all the internet, but found no similar resolved issues.
So, I'm playing around with Cloud Firestore and my issue is simply that I can't add anything to Firestore from console, I click on "Add collection", enter name, then generate random id for new document, and add a single string to it. After clicking "Save", nothing is added and screen still says "No data at this location yet". I tried reloading, logging off and in again, adding only empty collection, etc. Anyone knows what could be wrong? Maybe that's some bug because Firestore is in beta?

I was facing the similar issue, after a lot of research, I found out that there is an issue with chrome browser. Just open the same console with firefox browser, you will be able to do all the operations :)

I had the same issue. Try to go to the collection that you have created directly via parent path.
EDIT:
Sorry, I was wrong. Problem still occurs. Found out antivirus blocks these operations. I'm using kaspersky

Similar problem here. It works after I enable data collection on Kaspersky.

If there is no document in the collection, the collection disappears. The process is fairly fail-proof. You can enter 1 as the document name and 1 as the string field leaving the value blank and it will still write.
Try adding a different data type. Also, try and use one of the SDKs, the web (browser) or admin (Node.js) SDK to write (.set) data in a document firebase.firestore().collection("test").doc().set({"name":"john"}); with the test/open security rules in place.

NOTE:
Firebase does not accept undefined values by default.
Check your values: Having undefined values could well be the reason.

Following Xavi's advice, I found out that it worked on Safari, I then went back to the Chrome Firebase console and logged out of all accounts and re-logged in with the account I have Firebase access to, and I am now able to read and write from the console and also from my React app.

Related

Firebase realtime database location... NO NEXT BUTTON

I was trying to get Realtime Database on Firebase, but it doesn't show me a 'NEXT' button when I'm trying to get the database location.
I was following online tutorials which are supposed to look like this:
and I have no idea why it happens like this to mine only
Most likely the problem for not displaying the "Next" button is related to your browser. The simplest solution to solving this kind of issue is to try to use the Firebase Console on another browser.

How to check for live issues with google tag manager?

Previously working code that downloads a csv file from our site, now fails. Chrome, Safari and Edge don't display anything helpful except "Blob Blocked", but Firefox shows a stack trace;
Uncaught TypeError: Location.href setter: Access to 'blob:http://oursite.test/7e283bab-e48c-a942-928c-fae0907fdc82' from script denied.
Then a stack dump from googletagmanager
This appears to be a fault in the tagmanager code introduced in the last couple of weeks.
The fault appears in all browsers and is resolved immediately by commenting out the tag manager. The problem reported by a customer on the production system, and then found on both staging and locally. The customer advised they had used the export function successfully 2 weeks ago.
The question really is, do Google maintain a public facing issues log for things like the tag manager?
It's not about GTM as a library really, it's about poor user implementation. It's not up to Google to check for user-introduced conflicts with the rest of the site's functionality.
What you could do is go to GTM, and see what has been released in the past two weeks. Inspect things and look for anything that could interfere with the site's functionality. At the same time - do the opposite, see all the front-end changes introduced during this time frame by the web-dev team.
Things to watch for is mostly unclosured JS deployed in custom HTML tags. junior GTM implementation specialists like to use the global space, taking the global variables, often after the page is loaded, thus overwriting front-end's variables.
Sometimes, people would deploy minified unclosured code to the DOM, thus chaotically taking short var names. To the same end.
This is likely the easiest and most common way for GTM to break front-end. There definitely still are many ways to do so besides this though.
If this doesn't help, there's another easy way to debug it: make a new workspace from Default (or whatever is live), go into the preview mode and confirm that the issue still happens. Now start disabling newest created fired tags one by one and pinpoint which one causes the issue.
Let us know what it was.
Solution was to replace the previous tag manager code with the latest recommended snippet

Firestore webpage shows wrong data

I have a small problem that is driveing me crazy.
It seems that the Firestore Webpage is not showing my Database correctly.
If i add data via flutter it shows up immediately. And if i delete it again via code it dissapears like it should.
But if i delete in inside the Browser. It disapears but i can still access it via code.
The same thing applies to editing via the Browser. It changes visually but accessing via code i get the old Value. I thought i might be a delay so I waited until the next Day, but the web View and the code Values where still different.
Is this a Bug ?
.collection(FirebaseAuth.instance.currentUser!.uid)
.doc("SavedChain")
.snapshots()
.first;
This is how i access the data.
This is how i delete it
After deleting it, it disapears like it should. But i can still access it with the code above.
I suspect that snapshots().first gives you the cached value for the document. If that is the case, the solution is to use get() instead of those two calls:
.collection(FirebaseAuth.instance.currentUser!.uid)
.doc("SavedChain")
.get();

How to add login via Twitter functionality with Firebase?

I read the documentation on https://www.firebase.com/docs/ios/guide/login/twitter.html. I downloaded and added the two files as it says in the documentation. I also imported Accounts at the beginning of the files, so Xcode builds successfully. Then I copied the exact code in the documentation to my twitterLogin IBAction, and set my Twitter API Key and Firebase base reference.
The problem is that when I click on my twitter login button, nothing happens. (It used to say no twitter accounts, then I set my account in the Settings.) I even put print statements in any if-else case but none of them prints. So is there any suggestions for making Twitter login work? I don't think Firebase is missing anything. But please give some suggestions on how to figure out the issue at least.
Check to make sure that you have Enabled Twitter Authentication in your Firebase Dashboard, and that the apiKey in your project matches the one that is in your Dashboard.
Hope that helps :)
I solved the issue. The 'funny' solution was to add an equal sign to the condition
if accounts.count > 1
For anyone who is not lucky enough to notice that the sample code in the Firebase documentation is weirdly working only for users that have 'more' than 1 twitter account signed in the device, I believe this answer would help to save some time.
I also think that this sample code is misleading.(may be something that shouldn't be the default case in the sample code)
I have recently found some pretty good stuff on exactly this topic may it can help someone:
https://medium.com/reversebits/twitter-authentication-in-firebase-for-android-51d1460dc6a9#.strjpm90r

Google Tag Manager V2 Issue: "Invalid input. You may have stale data; refresh the page and try again." when creating new container

Keep getting this error when trying to create my first account/container in the new interface: http://screencast.com/t/GHla6fpBkRE
I found this discussion on github: "Failure to create container can leave behind state requiring manual intervention" - I'm guessing this is what I'm experiencing right now? How would i get someone to take a look at this? We are planning on moving tracking for several major properties in to GTM but we want to verify there won't be any issues with V2 first. Guess this isn't a great sign :P Everything works fine in my other Google account, it's just this one.
Just needed to create a tag, can't publish an empty container

Resources