title: App has not responded to the network requests below : while running the detox test ( Detox + Jest )
body: <p>My Setup</p>
  <p>detox : 18.0.0
  jest : 26.6.3
  react-native-cli : 2.0.1
  nodejs : 14.15.4
  npm  : 6.14.10
  yarn : 1.22.10
  OS   : ubuntu 18.04
  real connected device : Samsung M 01</p>
  <p><a href="https://i.stack.imgur.com/a7w22.png" rel="nofollow noreferrer">Please find the image on below url , after initialise the app by detox its not loading properly and this error screen is coming on connected device </a></p>
  <pre><code>My init.js 
  
  const detox = require('detox');
  const adapter = require('detox/runners/jest/adapter');
  const specReporter = require('detox/runners/jest/specReporter');
  
  // Set the default timeout
  jest.setTimeout(2000);
  
  jasmine.getEnv().addReporter(adapter);`enter code he`enter code here`re`
  
  // This takes care of generating status logs on a per-spec basis. By default, jest only reports at file-level.
  // This is strictly optional.
  jasmine.getEnv().addReporter(specReporter);
  
  beforeAll(async () =&gt; {
    await detox.init();
    device.launchApp();
  }, 300000);
  
  beforeEach(async () =&gt; {
    try {
      await adapter.beforeEach();
    } catch (err) {
      // Workaround for the 'jest-jasmine' runner (default one): if 'beforeAll' hook above fails with a timeout,
      // unfortunately, 'jest' might continue running other hooks and test suites. To prevent that behavior,
      // adapter.beforeEach() will throw if detox.init() is still running; that allows us to run detox.cleanup()
      // in that emergency case and disable calling 'device', 'element', 'expect', 'by' and other Detox globals.
      // If you switch to 'jest-circus' runner, you can omit this try-catch workaround at all.
  
      await detox.cleanup();
      throw err;
    }
  });
  
  afterAll(async () =&gt; {
    await adapter.afterAll();
    await detox.cleanup();
  });
  
  
  
  
  My Package.json :
  
  
    &quot;detox&quot;: {
      &quot;configurations&quot;: {
        &quot;android.emu.debug&quot;: {
          &quot;binaryPath&quot;: &quot;android/app/build/outputs/apk/debug/app-debug.apk&quot;,
          &quot;build&quot;: &quot;cd android &amp;&amp; ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug &amp;&amp; cd ..&quot;,
          &quot;type&quot;: &quot;android.attached&quot;,
          &quot;device&quot;: {
            &quot;adbName&quot;:&quot;R9BN90441KJ&quot;
          }
        },
        &quot;android.emu.release&quot;: {
          &quot;binaryPath&quot;: &quot;android/app/build/outputs/apk/release/app-release.apk&quot;,
          &quot;build&quot;: &quot;cd android &amp;&amp; ./gradlew assembleRelease assembleAndroidTest -DtestBuildType=release &amp;&amp; cd ..&quot;,
          &quot;type&quot;: &quot;android.emulator&quot;,
          &quot;name&quot;: &quot;Test Kirana&quot;
        }
      },
      &quot;specs&quot;: &quot;e2e&quot;,
      &quot;test-runner&quot;: &quot;jest&quot;
    },
    &quot;rnpm&quot;: {
      &quot;assets&quot;: [
        &quot;android/app/src/main/assets/fonts/Roboto/Roboto-Regular.ttf&quot;
      ]
    }
  </code></pre>
  <p>Please find Error messages below :</p>
  <p>detox[10532] WARN:  [Client.js/PENDING_REQUESTS] App has not responded to the network requests below:</p>
  <p>HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for &quot;ready&quot; message (over WebSocket) from the instrumentation process.
  (Use <code>node --trace-warnings ...</code> to show where the warning was created)</p>
  <p>Jest did not exit one second after the test run has completed.</p>
  <p>detox[10520] ERROR: [cli.js] Error: Command failed: jest --config e2e/config.json --testNamePattern '^((?!:ios:).)*$' --maxWorkers 1 e2e/01-placeorder_from_all_page.spec.js</p>