Run on Mac Silicon processor about whatsapp-http-api

[allburov]

@martinmineo hi!
I think the bug is related to chromium, but I can not test it and properly debug (don't have Macbook pro M1).
We probably will have to support two version of docker image - like devlikeapro/whatsapp-http-api:arm

Please feel free to open pull requests with the issue's fix!

If anyone else encountered the same issue - please hit thumb up 👍 on the first comment - we'll know how many of people experience the issue.

[martinmineo]

@allburov I wish I knew how to fix it!

[allburov]

@martinmineo btw, for Mac users the easiest way to work with the project - purchase a VPS with 2CPU and Ubuntu (I tried with 1CPU but it's too slow)
In DigitalOcean it costs about $24 https://www.digitalocean.com/

[martinmineo]

Yes, I will do something like that!
For testing purposes, I used another computer with an Intel processor and it works great! Amazing job!!

[allburov]

Hi!
We've published tags for ARM architecture - devlikeapro/whatsapp-http-api:arm and devlikeapro/whatsapp-http-api-plus:arm
There's a note how to install the right docker image

@martinmineo could you try this one on your Mac when you have time please?

[martinmineo]

Hi! It seems that there's still something to be fixed
Note: I'm using the PLUS version

{
  "statusCode": 500,
  "timestamp": "2023-02-28T11:45:55.359Z",
  "exception": {
    "stack": "Error: Evaluation failed: Error: wid error: invalid wid\n    at new c (https://web.whatsapp.com/app.208e5a49d844a8c35245.js:68:45641)\n    at Object.s [as createWid] (https://web.whatsapp.com/app.208e5a49d844a8c35245.js:68:50862)\n    at __puppeteer_evaluation_script__:2:53\n    at ExecutionContext._evaluateInternal (/app/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async ExecutionContext.evaluate (/app/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:16)\n    at async Client.sendMessage (/app/node_modules/whatsapp-web.js/src/Client.js:686:28)\n    at async /app/node_modules/@nestjs/core/router/router-execution-context.js:46:28\n    at async /app/node_modules/@nestjs/core/router/router-proxy.js:9:17",
    "message": "Evaluation failed: Error: wid error: invalid wid\n    at new c (https://web.whatsapp.com/app.208e5a49d844a8c35245.js:68:45641)\n    at Object.s [as createWid] (https://web.whatsapp.com/app.208e5a49d844a8c35245.js:68:50862)\n    at __puppeteer_evaluation_script__:2:53",
    "name": "Error"
  },
  "request": {
    "path": "/api/sendText",
    "method": "POST",
    "body": {
      "chatId": "XXXXXXXXXXXX.us",
      "text": "Hi there!",
      "session": "my-session"
    },
    "query": {}
  },
  "version": {
    "version": "2023.3.1",
    "tier": "PLUS",
    "browser": "/usr/bin/chromium"
  }
}

[allburov]

@martinmineo Could you check the chatId that you used there? It looks like it contains + at the start

I've put it in format [email protected] (where 123123123 is my real number) and it works, but with [email protected] it showed the same error, invalid wid

The same happens when you put a random number, like [email protected]

[martinmineo]

It's not including the "+", this is the body I used (I will change some numbers with "X" to keep privacy)

"body": {
      "chatId": "54XXXXXXXXX68.us",
      "text": "Hi there!",
      "session": "54XXXXXXXXXX33"
    },

[martinmineo]

ooooh I've realized that there's a missing "@c." in the chatId

I will try again

[martinmineo]

yes! It's working fine now. Thank you very much for adding this feature :)

[allburov]

@martinmineo thank you for testing the feature!