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

FirebaseInAppMessaging V9 (and other packages) modular APIs not exercised in CI?

Open mikehardy opened this issue 2 years ago • 8 comments
trafficstars

          FirebaseInAppMessaging V9 modular APIs not exercised in CI

Not sure exactly why coverage is showing up as not hitting these APIs when the tests seem to cover them Don't want to block the PR though so this is a separate issue

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

mikehardy avatar Sep 04 '23 22:09 mikehardy

This appears to be a common item, expanding this to include the new database module (in progress) as it is annotated as not covered, and it may affect all modules somehow.

mikehardy avatar Sep 19 '23 15:09 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 Oct 17 '23 16:10 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 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]

Not stale

exaby73 avatar Jan 15 '24 06:01 exaby73

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 12 '24 07:02 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 Mar 26 '24 15:03 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 May 02 '24 10:05 github-actions[bot]