react-native-firebase icon indicating copy to clipboard operation
react-native-firebase copied to clipboard

investigate the source behavior for firebase named queries on collections cached locally from loaded bundles

Open mikehardy opened this issue 1 year ago • 5 comments

investigate the source behavior for firebase named queries on collections cached locally from loaded bundles, that behavior has changed in android and ios SDKs since prior versions

Originally posted by @mikehardy in https://github.com/invertase/react-native-firebase/issues/7157#issuecomment-1575958097

mikehardy avatar Jun 05 '23 02:06 mikehardy

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Jul 03 '23 03:07 github-actions[bot]

I don't have a link handy but there is a possible upstream issue related to this where if I understand correctly the reported source behavior is shown incorrectly vs the actual source on some queries

mikehardy avatar Oct 20 '23 16:10 mikehardy

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Nov 17 '23 16:11 github-actions[bot]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Jan 01 '24 16:01 github-actions[bot]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Feb 27 '24 18:02 github-actions[bot]