Skip to content

Conversation

@russellwheatley
Copy link
Member

Description

Related issues

Release Summary

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
    • Yes
  • My change supports the following platforms;
    • Android
    • iOS
    • Other (macOS, web)
  • My change includes tests;
    • e2e tests added or updated in packages/\*\*/e2e
    • jest tests added or updated in packages/\*\*/__tests__
  • I have updated TypeScript types that are affected by my change.
  • This is a breaking change;
    • Yes
    • No

Test Plan


Think react-native-firebase is great? Please consider supporting the project with any of the below:

…l` (#8774)

Co-authored-by: Mike Hardy <github@mikehardy.net>
@russellwheatley russellwheatley removed the blocked: react-native Issue or PR blocked by a React Native issue or change. label Nov 28, 2025

describe('onConfigUpdate', function () {
// SKIPPED: Skipping suite of onConfigUpdate tests until they're fixed
describe.skip('onConfigUpdate', function () {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I cherry-picked this commit to a clean branch for separate PR to get it in now for all PRs until fixed, once it merges to main for everyone's benefit you'll want to rebase it out over on this PR. Cool feature, but such a hassle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants