firebase-js-sdk | Firebase Javascript SDK | Authentication library

Found out the solution on my own after a lot of search. Although I had to make a new bare react native project from scratch, and even then I was encountering that error, I had literally lost hope with firebase at that point. Then after sometime I changed my firebase config to the below code and it worked:

If Parent's propertyA is of type string, Child's propertyA must also be of type string, because of the Liskov substitution principle. A Child has to "be a" Parent, and that means that code with a Parent reference to a Child object must be able to treat it as though it were a Parent object. That code will expect a string, not a number.

Since that's not the case for what you're doing, inheritance probably isn't the appropriate approach. You might try composition instead: Child could have a field of type Parent.

Alternatively, have Child leave propertyA alone and have another property for the number.

Your code is only running once instead of running every time the auth state is updated. If you want to listen to any changes to the auth state, use a callback along with onAuthStateChanged as described here.

https://firebase.google.com/docs/auth/web/manage-users#get_the_currently_signed-in_user

A few Google services (like AdMob: https://developers.google.com/admob/android/charles) have documentation on how to read network traffic with Charles Proxy but I think your question is, if it’s possible with Cloud Firestore since Charles has support for protobufs.

The answer is : it is not possible right now. The firestore requests can be seen, but can't actually read any of the data being sent since it's using protocol buffers. There is no documentation on how to use Charles with Firestore requests, there is an open issue(feature request) on this with the product team which has no ETA. In the meanwhile, you can try with the Protocol Buffers Viewer.

Alternatives for viewing Firestore network traffic could be :

From Firestore documentation,

For all app types, Performance Monitoring automatically collects a trace for each network request issued by your app, called an HTTP/S network request trace. These traces collect metrics for the time between when your app issues a request to a service endpoint and when the response from that endpoint is complete. For any endpoint to which your app makes a request, Performance Monitoring captures several metrics:

• Response time — Time between when the request is made and when the response is fully received
• Response payload size — Byte size of the network payload downloaded by the app
• Request payload size — Byte size of the network payload uploaded by the app
• Success rate — Percentage of successful responses compared to total responses (to measure network or server failures)

You can view data from these traces in the Network requests subtab of the traces table, which is at the bottom of the Performance dashboard (learn more about using the console later on this page).This out-of-the-box monitoring includes most network requests for your app. However, some requests might not be reported or you might use a different library to make network requests. In these cases, you can use the Performance Monitoring API to manually instrument custom network request traces. Firebase displays URL patterns and their aggregated data in the Network tab in the Performance dashboard of the Firebase console.

From stackoverflow thread,

The wire protocol for Cloud Firestore is based on gRPC, which is indeed a lot harder to troubleshoot than the websockets that the Realtime Database uses. One way is to enable debug logging with:

I can get it to work by using this setting:

chnage the .js file to

I don't know why but the new versions of the package don't work well and the method is no longer in, I downgraded the package to version "^1.3.7".

Change in your package.json:

The documentation has a complete code snippet explaining how to fetch a single document with given ID:

Insert window.addEventListener = x => x; at the top level of your app.

There is no global window.addEventListener function in React Native. The execution environment is different from a web browser.

(errors installing Firebase)

You can install firebase@8.2.3 - yarn add firebase@8.2.3 and I believe they've removed the grpc dependency in that version. Building native dependencies for Node packages commonly fails on Windows machines for a variety of reasons, you should search issues on repositories related to those packages for more information when you encounter in the future. eg: https://github.com/grpc/grpc-node/issues/1183