Warning: You called act(async () => ...) without await. 2 minute repro on examples/reactnavigation

Describe the bug

I see the infamous Warning: You called act(async () => ...) without await. after a fresh clone and install checking out the reactnavigation example.

Expected behavior

No warnings. I thought react-native-testing-library is supposed to wrap all async actions in act already? I guess and use await

Steps to Reproduce

1. Clone this repository: git clone https://github.com/callstack/react-native-testing-library.git
2. Move into the proper example: cd react-native-testing-library/examples/reactnavigation
3. Install packages: npm install (You need npm install --legacy-peer-deps if you are using a newer version of Node)
4. Run tests: npm run test
5. See warnings in test output:

console.error
      Warning: You called act(async () => ...) without await. This could lead to unexpected testing behaviour, interleaving multiple act calls and mixing their scopes. You should - await act(async () => ...);

Versions

npmPackages:
    @testing-library/react-native: ^7.0.0-rc.0 => 7.2.0 
    react: ^16.13.1 => 16.14.0 
    react-native: ^0.62.2 => 0.62.3 
    react-test-renderer: ^16.13.1 => 16.14.0

[teves-castro]

The thing is @pierrezimmermannbam that when you actually need to use findBy (or any kind of await for async operation) twice in the same test, you’ll always have the warning.

[pierrezimmermannbam]

I believe this happens when calling several times await findByText in a row though I’m not sure why. In this example the tests don’t need to be asynchronous so removing async and using getBy instead of findBy works fine and it makes the warning go away. I also think it’s a bad pattern to use findByText by default and to make all tests asynchronous when it is not necessary, so I’d recommend either changing the example so that we really need to use waitfor in the tests or using plain getByText