Error: Requesting main frame too early!

[rmp1985]

Guys, my Venom connects for about 24 hours and then it simply doesn't respond with .sendText anymore

In the log this starts to appear:

• Successfully main page!
  Error: Requesting main frame too early!
  at assert (/srv/api-whatsapp/node_modules/puppeteer/node_modules/puppeteer-core/lib/cjs/puppeteer/util/assert.js:18:15)
  at FrameManager.mainFrame (/srv/api-whatsapp/node_modules/puppeteer/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/FrameManager.js:213:32)
  at CdpPage.mainFrame (/srv/api-whatsapp/node_modules/puppeteer/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Page.js:406:35)
  at CdpPage.evaluate (/srv/api-whatsapp/node_modules/puppeteer/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Page.js:841:31)
  at /srv/api-whatsapp/node_modules/venom-bot/dist/api/layers/sender.layer.js:327:44
  at new Promise ()
  at Whatsapp.sendText (/srv/api-whatsapp/node_modules/venom-bot/dist/api/layers/sender.layer.js:304:16)
  at action (/srv/api-whatsapp/src/controllers/sendTextController.js:16:41)
  at comunicaWhatsApp (/srv/api-whatsapp/src/services/comunicaWhatsApp.js:20:7)
  at exports.sendTextHandler (/srv/api-whatsapp/src/controllers/sendTextController.js:18:16)
  at Layer.handle [as handle_request] (/srv/api-whatsapp/node_modules/express/lib/router/layer.js:95:5)
  at next (/srv/api-whatsapp/node_modules/express/lib/router/route.js:149:13)
  at Route.dispatch (/srv/api-whatsapp/node_modules/express/lib/router/route.js:119:3)
  at Layer.handle [as handle_request] (/srv/api-whatsapp/node_modules/express/lib/router/layer.js:95:5)
  at /srv/api-whatsapp/node_modules/express/lib/router/index.js:284:15
  at Function.process_params (/srv/api-whatsapp/node_modules/express/lib/router/index.js:346:12)

Is anyone going through this?

It started about 2 weeks ago. Before, the connection was active normally without dropping.

[caetano157]

This happened to me when I made the connection via terminal on the same machine where I was shooting via RPA integration.
Sometimes it was necessary to kill the chrome process for the RPA to work normally and this would freeze the connection via terminal with venom-bot
I don't know if the scenario is the same but maybe this can help you solve your problem

[9cb14c1ec0]

This repo has been abandoned. Check out our actively maintained fork at venomlib/venom