-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support For Firestore collectionGroup #2305
Comments
No template |
checkout their feedback page https://invertase.io/oss/react-native-firebase/feedback/p/add-collectiongroup-query-support |
That link is broken @BartJanvanAssen. Please is there any plan to support this in v5? Thanks so much |
I really need this functionality as well @BartJanvanAssen and I'm on v5 now. |
This is possible in v5 but it's not as simple to implement due to the way the module is setup. Once we get v6 out we may backport it however we have to really focus on v6 at the moment. Happy to accept a PR on this and review. |
@Ehesp When is v6 expected to release? I've tried to look at bit into v6, but it seems unclear to me how far you are with it. Is there any guides on how to upgrade from v5 to v6? |
@holgersindbaek apart from AdMob and Notifications, it's all "working" (apart from some build error/setup bugs). Re migration - planning on writing that soon... I'll post in here once I get there. |
@Ehesp Thanks. The faster, the better. I really need the collectionGroup functionality. |
+1 for v5 |
We won't be adding collection group to v5 I'm afraid unless it's from a community contribution. |
I know this is old thread, but this might help others who wants to stick with v5. I was facing the same issue while using v5, I upgraded to v6 but the push notification is not working, and I don't want that. I found my solution: then (after config ) : |
Unhandled JS Exception: TypeError: TypeError: _reactNativeFirebase.default.firestore(...).collectionGroup is not a function
This issue is happening for both iOS and Android.
The text was updated successfully, but these errors were encountered: