'document' is become null randomly in amplify.

[nickoan]

🐛 Bug Report

error message:

TypeError: Cannot read property 'body' of null at getActiveElement

the unit test will randomly fail because of top exception.
and it not just occurring in a specific unit test. it can be anywhere a cross of different test case.

some of test even not using DOM object.

example:

test('example' , async () => {
    expect(
      // doing some validate checking using aws sdk.
      await validateAwsTokenMethod(token, validUserInfo)
    ).toEqual(invalidCognitoExpectedResult);
  });

and I'm using:
jest: 24.9.0
also was tried change to jest-environment-jsdom-thirteen.
same happens.

any idea about this case?
Thanks.

To Reproduce

it is working fine in my mac and the docker containers (eg. awslinux2, ubuntu) in my mac.
but in AWS amplify, it's occurring sometimes, maybe (30% probability);

Expected behavior

the document should not be null.

Link to repl or repo (highly encouraged)

envinfo

Linux 4.14.143-91.122.amzn1.x86_64
"/root/.nvm/versions/node/v10.16.0/bin/node" "/root/.nvm/versions/node/v10.16.0/bin/npm" "run" "test-coverage"
node v10.16.0
npm  v6.9.0

[eps1lon]

Can reproduce with Jest 27 in https://github.com/eps1lon/react-testing-library-error-repro/blob/jest-repro/ (reduced repro from testing-library/react-testing-library#1027)

[SimenB]

@eps1lon could you open up a new issue with that reproduction? This issues doesn't have one, so I'll close it as it isn't actionable on its own

[eps1lon]

Continued in #12670

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.