search

open-wa / wa-automate-nodejs

💬 🤖 The most reliable tool for chatbots with advanced features. Be sure to 🌟 this repository for updates!
https://docs.openwa.dev/
Other
3.05k stars 588 forks source link

Error upon restarting application: Checking session integrity > Session integrity check failed, trying again... 2 > WAPI inject: 3ms #3180

Closed TVARecordings closed 2 months ago

TVARecordings commented 3 months ago

Are you using the latest version of the library?

What type of session are you experiencing this issue on?

Multi-device and I have set multiDevice to true in my config OR am using the --multi-device flag

What type of host account are you experiencing this issue on?

Personal account (normal)

Mode

EASY API/CLI

Current Behavior

Dear SHAH.

Recently my Host-number was changed, i deleted the session data etc and connected the new host. The first connection goes without a flaw. However, upon restarting the session after waiting at least 10 minutes, it returns this error: Checking session integrity Session integrity check failed, trying again... 55 WAPI inject: 2ms

Expected Behavior

Just boot up like it did in the past.

Steps To Reproduce

Step 1: Connect new host. Step 2: Wait anywhere between 10 minutes and infinite hours. Step 3: Close the application (npx pm2 stop index.js or close cmd.exe if using npm start) Step 4: Start the application again (_npx pm2 start index.js or cmd.exe npm start) Step 5: Watch the output :D

create() code OR full CLI command + CONFIG

const configObject = {
  sessionId: 'aNewNameEachTimeTheSessionFails',
  authTimeout: 0,
  cacheEnabled: true,
  useChrome: true,
  cachedPatch: true,
  devtools: false,
  chromiumArgs: ['--no-sandbox'],
  disableSpins: true,
  headless: false, //new
  popup: false,
  qrTimeout: 0,
  messagePreprocessor: "AUTO_DECRYPT", 
  linkParser: "https://link.openwa.cloud/api",
  restartOnCrash: true,
  logInternalEvents: false, //ONLY TURN THIS ON IF ASKED TO!
  discord: 'That's a secret!',
  ezqr: true,
  callTimeout: 60000, // 600000
  licenseKey: "Mine <3", 
  screenshotOnInitializationBrowserError: false,
  hostNotificationLang: 'nl-nl',
  killProcessOnBrowserClose: true,
  killProcessOnTimeout: false,
  logConsole: false,
  logConsoleErrors: true,
  logFile: true,
  onError: "LOG_AND_FALSE",
};

DEBUG INFO

{
  "WA_VERSION": "2.3000.1012447370",
  "WA_AUTOMATE_VERSION": "4.68.0",
  "BROWSER_VERSION": "Chrome/123.0.6312.86",
  "START_TS": 1711987673274,
  "RAM_INFO": "Total: 68.62 GB | Free: 46.63 GB",
  "PPTR_VERSION": "19.11.1",
  "LATEST_VERSION": true,
  "CLI": false
}

Environment

- OS: Windows 10
- Node: 20.11.1
- npm: 10.2.4

Screenshots/Logs

No response

Anything else?

Thanks for your hard work :-)

victorfreire100 commented 3 months ago

I have the same problem. :(

therealnotaslimboy commented 3 months ago

Same problem here, is it because of whatsapp changed their framework?

itzharDev commented 3 months ago

same problem

dmzoneill commented 3 months ago

same problem

TVARecordings commented 3 months ago

Same problem here, is it because of whatsapp changed their framework?

Most likely yes.

victorfreire100 commented 3 months ago

Could it be that this repository died again? no updates :(

donnyirianto commented 3 months ago

any update?

TVARecordings commented 3 months ago

Could it be that this repository died again? no updates :(

No. If you join their Discord-server, you’ll be kept up-to-date.

Right now, WhatsApp updated their framework. Back in March this was already announced as a future problem, as this Framework-update was expected.

They assume it from now takes aprox 2 weeks to fix.

smashah commented 2 months ago

3184

Please update to the latest version and try again thanks