React Native: Jest did not exit one second after the test run completed

[flextremedev]

Describe the bug
When testing react native code that uses react-query you'll get the following error:

Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to troubleshoot this issue.

To Reproduce
Steps to reproduce the behavior:

1. Clone https://github.com/flextremedev/ReactNativePlayground
2. Run "yarn"
3. Run "yarn test react-query"
4. See error

Expected behavior
I expected the test run to complete without leaving open handles.

[TkDodo]

have you seen #1692 ?

[flextremedev]

Yes, it's me again :)

[TkDodo]

Oh lol, sorry. I thought I checked the usernames 🙈 . I hope that someone with more knowledge (than me) of react-native and jest can tell us here how to proceed :)

[flextremedev]

The problem is setTimeout for cacheTime which is 5 minutes by default. When I set cacheTime to 0 jest stops complaining.

One solution would be to use jest.useFakeTimers() but this doesn't work with waitFor from testing-library/react-native and testing-library/hooks as of now.

[flextremedev]

jest.useFakeTimers can be used as soon as @testing-library/react-native v8.0.0 is released.
It works with v8.0.0-rc.0.
This is an okay solution but I would also love to be able to clear the cacheTimeout at the end of my tests but queryClient.clear doesn't work for me. Am I just using the wrong function?

[tannerlinsley]

Where are we on this? Are you still having issues @flextremedev >?

[flextremedev]

Yes. This won't be a much of a problem as soon as @testing-library/react-native has released v8. But it would still be nice to be able to clean up / clear the cacheTimeout in afterEach or at the end of a test. Unfortunately I couldn't get this to work as mentioned above.

[baptooo]

Hello ! I have the same issue here on a react-native based project

• @testing-library/react-native@7.2.0
• react-query@3.12.0
• jest@25.5.4
• @testing-library/jest-native@4.0.1

But setting a cacheTime of 0 in the QueryClient did the trick :)

[TkDodo]

But setting a cacheTime of 0 in the QueryClient did the trick :)

that makes sense because the timer is likely related to garbage collection, which depends on cacheTime. It can be set globally on the QueryClientProvider that you are using in the tests, so it won't influence production.

Is that workaround, plus the proposed fix with @testing-library/react-native v8 (still in rc) enough to close this issue?

[matthieugicquel]

I encountered the same issue.

It does not seem to happen when cacheTime is 0 OR Infinity.

In my tests the afterEach(() => { queryClient.clear() }); workaround solved it, but it seems ugly (have to put the client in a module top-level variable).

@TkDodo I don't think setting cacheTime globally will work if you override it in specific useQuery calls ?

[mefjuu]

In my tests the afterEach(() => { queryClient.clear() }); workaround solved it, but it seems ugly (have to put the client in a module top-level variable).

Right after creating queryClient instance before tests, I set:
queryClient.setDefaultOptions({ queries: { cacheTime: 0 } })