MichaelV00

Could be caused from a breaking change android side it sounds like, my guess is a native issue, I am open to checking out a minimal repro for this.

Hi there feel free to open a PR with this in mind if you like and we can properly evaluate it 😄

You can safely ignore that so don't worry about it too much 😄 . We are currently undergoing full typescript migrations so this issue will disappear as a result anyways.

Hi there, I don't seem to be able to reproduce this, could you provide a repo I could clone and investigate further? Could you also show any log output you...

Hi there, I was able to get it working by importing FirebaseFirestoreTypes and casting using that. e.t.c This should expose the types and get rid of the linter error. ```...

> For the limit, yes. But passing that reference to `getDocs` will still result in `any` instead of a properly typed snapshot. And we don't really want to do `const...

I am suspecting this issue could stem from a stale dependency that hasn't been updated hence why the workaround works as it forces us to not use that one. You...

> with `npx react-native config` the `packageImportPath` seems to be displayed correctly but it is not applied as expected on android during build. > > Very strange issue. Thats also...

Hi there @WontakKim looks good to me just fix the linter issues please and I will approve it and ensure the CLA is signed.

Hi there ``` import analytics from '@react-native-firebase/analytics' analytics().logScreenView({ screen_name: 'test', screen_class: 'test' }) ``` This is the name-spaced API, the docs are yet to be updated to only use modular...