`waitFor` with nested `expect` timeout in v9

Describe the bug

Hey guys, I’ve been banging my head for hours following a migration to v9. I had some timeout issues with a waitFor and I thought it was related to the timers thingy, but in fact in seems related to a nested expect in my waitFor it looks like it could be related to timers.

This works:

await screen.findByA11yRole('progressbar', { interval: 10 }); // Need more aggressive interval to catch the spinner before it is removed
waitForElementToBeRemoved(() => screen.getByA11yRole('progressbar'));

This doesn’t and acts weird:

await screen.findByA11yRole('progressbar', { interval: 10 }); // Need more aggressive interval to catch the spinner before it is removed
await waitFor(() => {
  expect(screen.queryByA11yRole('progressbar')).toBeFalsy();
});

When debugging the waitFor it appears to ignore interval or even timeout settings and is executed only twice, once right away and once when the default timeout hits.

Expected behavior

To work

Steps to Reproduce

Feels like this should be easily reproducible. I’ll look into it if not.

Screenshots

Versions

    @testing-library/react-native: ^9.0.0 => 9.0.0 
    react: 17.0.2 => 17.0.2 
    react-native: 0.65.1 => 0.65.1 
    react-test-renderer: ^17.0.2 => 17.0.2 ```

[florian-milky]

Sorry didn’t have time to really follow up on that. I will test again with the latest version and report at least

[mdjastrzebski]

Closing as stale.

@florian-milky If the issue still occurs on the latest version of RNTL, please provide a minimal repro repository, hopefully based on examples/basic folder from our repo, so that we can better understand the issue.