beforeAll() timesout when running e2e on bitrise (not happening on local)

Question & Answer
1

My e2e tests are running normally on my local environment, but they’re failing when running with bitrise. It is failing when trying to execute beforeAll():

  ● ARA › Create ARA but not be able to save because empty fields › 😡 On empty sector › should show "Create ARA" label
    thrown: "Exceeded timeout of 180000 ms for a hook.
    Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
      4 |
      5 | describe('ARA', () => {
    > 6 |   beforeAll(async () => {
        |   ^
      7 |     console.debug('Launching app...');
      8 |     await device.launchApp({ delete: true });
      9 |     console.debug('App launched.');
      at beforeAll (e2e/app/ARA/01_ARA_create_empty_fields.test.js:6:3)
      at Object.describe (e2e/app/ARA/01_ARA_create_empty_fields.test.js:5:1)
  ● ARA › Create ARA but not be able to save because empty fields › 😡 On empty sector › should show "Create ARA" label
    The pending request #2 ("invoke") has been rejected due to the following error:
    Detox has detected multiple interactions taking place simultaneously. Have you forgotten to apply an await over one of the Detox actions in your test code?
      26 |   describe('Create ARA but not be able to save because empty fields', () => {
      27 |     beforeAll(async () => {
    > 28 |       await element(by.id('add-ara-button')).tap();
         |                                              ^
      29 |     });
      30 |
      31 |     describe('😡 On empty sector', () => {
      at Object.tap (e2e/app/ARA/01_ARA_create_empty_fields.test.js:28:46)
      at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
      at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
      at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
      at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)

I have tried the solution given in this issue which was running npm rebuild detox, as I have the same problem, but it did not helped.
You can find my build here.
You will notice that I have stopped it to avoid consuming more credits, as I saw that it was throwing timeout error already.