In NavigationContainer.tsx, _warnedNoClient and _warnedNoIntegration are module-level singletons. jest.clearAllMocks() in beforeEach resets mock call counts but not these flags, so if a test that triggers a warning runs before another test asserting on the same warning mock, the second assertion will fail. Consider resetting these flags via a test-only export or using jest.resetModules().

NavigationContainer.tsx declares three module-level booleans (_warnedMissing, _warnedNoClient, _warnedNoIntegration) that are set to true on first trigger and never reset. The test suite's beforeEach calls only jest.clearAllMocks(), which does not reset module state. Currently each warning branch is asserted in exactly one test, so the suite passes; however, if either of the two warning tests is duplicated, reordered, or a new test exercises the same branch, debug.warn/debug.log will not fire again and the assertion will silently fail. Consider adding jest.resetModules() (with dynamic re-import) or jest.isolateModules around the warning tests, or exposing a test-only reset helper to keep these assertions robust.

Also found at:

• packages/core/test/NavigationContainer.test.tsx:56

The three module-level booleans (_warnedMissing, _warnedNoClient, _warnedNoIntegration) are set once per process lifetime; jest.clearAllMocks() in beforeEach does not reset them, so any new test that exercises the same warning path will silently skip the debug.warn/debug.log assertion.