Farewell, Webpack! Re-injection, Pairing Code login, and 2.24x jumbofix #2816

PurpShell · 2024-03-14T09:33:16Z

TL;DR:

WhatsApp released 2.3000x, a version that does not use Webpack anymore. We had to change the Store system to no longer use moduleRaid. Instability issues are caused by relying on selectors & DOM Observers for login, as well as increased performance issues. This prompted me to adopt the "New startup flow" that I mentioned here. This update is important. This update will boost reliability in WWebJS at least 400%. I also added pairing code login for those who needed it since I had the docs on hand (I reverse engineer then take notes, so I know what I know when I make them into PRs). It changes a lot in the authentication and launching. I advise you all to test your systems before deploying to production (even though this build should be prod-safe).

You should immediately update to my version and cease using any other fork or version. Your system will work regardless if you are using a web cache, local cache, no cache.. LocalAuth, RemoteAuth, NoAuth... 2.24 and 2.3000.

TO INSTALL:

npm install github:pedroslopez/whatsapp-web.js#webpack-exodus

If you encounter a git not found error in the NPM/yarn install: Download git, https://git-scm.com

Thank you for your trust and time and thank you to my sponsors for their contribution.

PR Details

This PR adds support for Wwebjs past version 2.3000.x and 2.24..x. Send "F" in the chat for Webpack!

As always, very big thanks to my sponsors for their support! I am only able to do this thanks to them!

Also thanks to @allburov for his work on #2827, helped me a bit to know which modules are problematic.

This PR also adds re-injection in the case of navigation or refresh or intentional logout and pairing code login option.

It also changes a lot of the code in the startup flow.

To note:

AUTHENTICATED and READY will now depend on the Socket, so if the WWebJS restarts or loses Internet, it will trigger these events. Do not trust that the event will only be triggered once.
await client.initialize() returns it promise much earlier at the point of a new QR code (no login). The behavior is almost the same when logged in (it resolves the promise at AROUND ready).
The Loading screen text will be hard-coded to "WhatsApp" for now. A new update will deprecate this screen text and replace it with loading types (ORGANIZING, INTIAL_LOAD, DOWNLOADING,...)
A new AuthStore is exposed at the time of initial load (before READY) including moduleRaid (2.24) and some modules needed for authentication.

This update will bring a lot of performance, time savings and increased reliability due to this refactor. We are not relying on constantly changing and dynamic HTML to get QR codes, to detect logins and this will make it much better. I also went out of my way and reversed all of the Pairing Code infra to get the only needed functions (3) and made them into this way so that we stop getting failed attempts like #2363

Description

Related Issue

closes #2789, closes #1787, closes #3016

Motivation and Context

After WhatsApp's update to 2.3000.x, moduleRaid no longer detected webpack (since they changed build systems)
After WhatsApp's update to 2.24xx.x, the manifest json no longer included the version, requiring a revamp for the cache system!

How Has This Been Tested

I tested this on many machines and concluded it is non-obtrusive. This will not break old versions and works with new ones

Types of changes

Dependency change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

My code follows the code style of this project.
I have updated the documentation accordingly (index.d.ts).

ricardoapaes · 2024-03-14T12:26:14Z

Good morning, but it's not running here because it doesn't find this require "__debug", how do I solve it?

complanboy2 · 2024-03-14T17:21:36Z

Also, the "eval" function from inject.js file isn't running due to content security policy !!

Shinhwe · 2024-03-15T01:24:50Z

Good morning, but it's not running here because it doesn't find this require "__debug", how do I solve it?

try this
Object.values(window.require('__debug').modulesMap

PurpShell · 2024-03-16T15:26:35Z

Good morning, but it's not running here because it doesn't find this require "__debug", how do I solve it?

Check the latest moduleRaid version

PurpShell · 2024-03-16T15:26:58Z

Good morning, but it's not running here because it doesn't find this require "__debug", how do I solve it?

try this Object.values(window.require('__debug').modulesMap

pretty sure I did that, I will see if I didn't

voidpack · 2024-03-17T08:21:58Z

using nodejs v13 after apply new moduleraid on whatsapp web version Version 2.3000.1012111500 still got error

(node:10784) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')

MoudiZd · 2024-03-17T10:35:42Z

using nodejs v13 after apply new moduleraid on whatsapp web version Version 2.3000.1012111500 still got error

(node:10784) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')

I believe that the issue is not in the pr itself but in the way moduleRaid is used and the way is finding modules, used within injected.js, because in many cases it assumes that the findModule method returns non empty array, maybe with old webpack this way it was feasible but now with comet this code needs some optimization

I am not sure if the manipulation of these statements actually differs between node versions or between different modes, this need a lot of tests

complanboy2 · 2024-03-17T10:46:54Z

ModuleError: Requiring module "%s" with unresolved dependencies: %s

Getting this error

MoudiZd · 2024-03-17T11:40:14Z

ModuleError: Requiring module "%s" with unresolved dependencies: %s

Getting this error

Please if you can print the full error so we can see in which file and in which line this error is occured

complanboy2 · 2024-03-17T12:00:11Z

ModuleError: Requiring module "%s" with unresolved dependencies: %s
Getting this error

Please if you can print the full error so we can see in which file and in which line this error is occured

Thank you. I'm using module raid and the code from inject.js

voidpack · 2024-03-17T12:46:47Z

using nodejs v13 after apply new moduleraid on whatsapp web version Version 2.3000.1012111500 still got error
(node:10784) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')

I believe that the issue is not in the pr itself but in the way moduleRaid is used and the way is finding modules, used within injected.js, because in many cases it assumes that the findModule method returns non empty array, maybe with old webpack this way it was feasible but now with comet this code needs some optimization

I am not sure if the manipulation of these statements actually differs between node versions or between different modes, this need a lot of tests

maybe because i'm using backtick for this on module raid ? because without backtick it give error unexpected token '.' on nodejs v13

const isComet = parseInt(window.Debug?.VERSION?.split(".")?.[1]) >= 3000;

mouhammad-zd · 2024-03-17T13:24:00Z

using nodejs v13 after apply new moduleraid on whatsapp web version Version 2.3000.1012111500 still got error
(node:10784) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')

I believe that the issue is not in the pr itself but in the way moduleRaid is used and the way is finding modules, used within injected.js, because in many cases it assumes that the findModule method returns non empty array, maybe with old webpack this way it was feasible but now with comet this code needs some optimization
I am not sure if the manipulation of these statements actually differs between node versions or between different modes, this need a lot of tests

maybe because i'm using backtick for this on module raid ? because without backtick it give error unexpected token '.' on nodejs v13

const isComet = parseInt(window.Debug?.VERSION?.split(".")?.[1]) >= 3000;

Try to update your node version, as it seems that optional chaining is not supported in node older than node 14

voidpack · 2024-03-17T13:31:56Z

using nodejs v13 after apply new moduleraid on whatsapp web version Version 2.3000.1012111500 still got error
(node:10784) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')

I believe that the issue is not in the pr itself but in the way moduleRaid is used and the way is finding modules, used within injected.js, because in many cases it assumes that the findModule method returns non empty array, maybe with old webpack this way it was feasible but now with comet this code needs some optimization
I am not sure if the manipulation of these statements actually differs between node versions or between different modes, this need a lot of tests

maybe because i'm using backtick for this on module raid ? because without backtick it give error unexpected token '.' on nodejs v13
const isComet = parseInt(window.Debug?.VERSION?.split(".")?.[1]) >= 3000;

Try to update your node version, as it seems that optional chaining is not supported in node older than node 14

can't do it. because the client still using windows 7. latest support can only using node v13

MoudiZd · 2024-03-17T13:52:34Z

You must optimize code to use old javascript

using nodejs v13 after apply new moduleraid on whatsapp web version Version 2.3000.1012111500 still got error
(node:10784) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')

I believe that the issue is not in the pr itself but in the way moduleRaid is used and the way is finding modules, used within injected.js, because in many cases it assumes that the findModule method returns non empty array, maybe with old webpack this way it was feasible but now with comet this code needs some optimization
I am not sure if the manipulation of these statements actually differs between node versions or between different modes, this need a lot of tests

maybe because i'm using backtick for this on module raid ? because without backtick it give error unexpected token '.' on nodejs v13
const isComet = parseInt(window.Debug?.VERSION?.split(".")?.[1]) >= 3000;

Try to update your node version, as it seems that optional chaining is not supported in node older than node 14

can't do it. because the client still using windows 7. latest support can only using node v13

So you must optimize this statement to use old javascript

Try this:

var isComet = false;

if (window.Debug && window.Debug.VERSION) {
  var versionParts = window.Debug.VERSION.split(".");
  if (versionParts.length > 1) {
    var versionNumber = parseInt(versionParts[1]);
    isComet = versionNumber >= 3000;
  }
}

maunklana · 2024-03-18T04:49:58Z

I got this error

C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221
            throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));
                  ^

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')
    at __puppeteer_evaluation_script__:5:95
    at ExecutionContext._evaluateInternal (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ExecutionContext.evaluate (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16)
    at async Client.initialize (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\src\Client.js:339:9)

Node.js v20.9.0

the error was caused by a change in the function

so I change the injected.js remove all .default

window.Store = Object.assign({}, window.mR.findModule(m => m && m.Chat)[1]);
window.Store.Call = window.mR.findModule((module) => module && module.Call)[0].Call;

Tested Sending & Receive Message is ok.

Update
Got this Error on Sending message on some text or something.

Error: Evaluation failed: Error: Data passed to getter must include an id property (it's how we memoize) but got undefined
	at new Error (<anonymous>:5:31)
	at h (https://static.whatsapp.net/rsrc.php/v3/yO/r/rP20sdRimEJ.js?_nc_x=Ij3Wp8lg5Kz:70:191)
	at t (https://static.whatsapp.net/rsrc.php/v3iex14/yT/l/makehaste_jhash/JjfhzrFnzpi.js?_nc_x=Ij3Wp8lg5Kz:391:4493)
	at Object.d [as getLinkPreview] (https://static.whatsapp.net/rsrc.php/v3iex14/yT/l/makehaste_jhash/JjfhzrFnzpi.js?_nc_x=Ij3Wp8lg5Kz:391:2447)
	at window.WWebJS.sendMessage (__puppeteer_evaluation_script__:135:62)
	at async __puppeteer_evaluation_script__:10:25
	at ExecutionContext._evaluateInternal (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19)
	at process.processTicksAndRejections (node:internal\process\task_queues:95:5)
	at async ExecutionContext.evaluate (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16)
	at async Client.sendMessage (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\src\Client.js:930:28)

voidpack · 2024-03-18T06:53:11Z

I got this error

C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221
            throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));
                  ^

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')
    at __puppeteer_evaluation_script__:5:95
    at ExecutionContext._evaluateInternal (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ExecutionContext.evaluate (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16)
    at async Client.initialize (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\src\Client.js:339:9)

Node.js v20.9.0

the error was caused by a change in the function

so I change the injected.js remove all .default

window.Store = Object.assign({}, window.mR.findModule(m => m && m.Chat)[1]); window.Store.Call = window.mR.findModule((module) => module && module.Call)[0].Call;

Tested Sending & Receive Message is ok.

i try remove that 2 line .default still error reading 'default'
and then i try remove all the .default on injected and got error reading 'on'

using node v13 and whatsapp web Version 2.3000.1012116664 (did your web version like mine ? i found that after 2.3000.xxxxx the number xxxxx keep increasing, maybe whatsapp keep updating or what ?)

maunklana · 2024-03-18T07:01:22Z

try following this change #2822

I got this error
C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221
            throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));
                  ^

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')
    at __puppeteer_evaluation_script__:5:95
    at ExecutionContext._evaluateInternal (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ExecutionContext.evaluate (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16)
    at async Client.initialize (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\src\Client.js:339:9)

Node.js v20.9.0
the error was caused by a change in the function

so I change the injected.js remove all .default
window.Store = Object.assign({}, window.mR.findModule(m => m && m.Chat)[1]); window.Store.Call = window.mR.findModule((module) => module && module.Call)[0].Call;
Tested Sending & Receive Message is ok.
i try remove that 2 line .default still error reading 'default' and then i try remove all the .default on injected and got error reading 'on'

using node v13 and whatsapp web Version 2.3000.1012116664 (did your web version like mine ? i found that after 2.3000.xxxxx the number xxxxx keep increasing, maybe whatsapp keep updating or what ?)

voidpack · 2024-03-18T07:17:16Z

try following this change #2822
I got this error
C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221
            throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));
                  ^

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')
    at __puppeteer_evaluation_script__:5:95
    at ExecutionContext._evaluateInternal (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ExecutionContext.evaluate (C:\Users\Maunklana\Documents\ww\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16)
    at async Client.initialize (C:\Users\Maunklana\Documents\ww\node_modules\whatsapp-web.js\src\Client.js:339:9)

Node.js v20.9.0
the error was caused by a change in the function

so I change the injected.js remove all .default
window.Store = Object.assign({}, window.mR.findModule(m => m && m.Chat)[1]); window.Store.Call = window.mR.findModule((module) => module && module.Call)[0].Call;
Tested Sending & Receive Message is ok.
i try remove that 2 line .default still error reading 'default' and then i try remove all the .default on injected and got error reading 'on'
using node v13 and whatsapp web Version 2.3000.1012116664 (did your web version like mine ? i found that after 2.3000.xxxxx the number xxxxx keep increasing, maybe whatsapp keep updating or what ?)

thx finally fix it. I miss the array [0] change to [1]. thx you very much

DenysSamoiliuk · 2024-05-16T07:23:28Z

hi, please tell me if you know what caused this error Initialize error: Waiting for selector [data-icon='search'] failed: Protocol error (Runtime.callFunctionOn): Target closed. and how to deal with it, we use this branch in the project, but periodically when we have to reload the docker container in k3s we get this log when initializing the session. I use version 2.3000.xxxx and also the latest 2.24xxx, but I got the same result

tofers · 2024-05-17T08:03:51Z

Update the branch with main, please
I need to check vote_update

TechnVision · 2024-05-17T18:06:17Z

node_modules/whatsapp-web.js/index.d.ts:124:49 - error TS2371: A parameter initializer is only allowed in a function or constructor implementation.

124 requestPairingCode(phoneNumber: string, showNotification = true): Promise

I'm this error on logon easy fix requestPairingCode(phoneNumber: string, showNotification: true): Promise<string>

wildandahru · 2024-05-19T08:12:35Z

after install npm install github:pedroslopez/whatsapp-web.js#webpack-exodus qrcode didn't show up. I tried to change headless to false and the qr just stuck in load state.

tofers · 2024-05-19T08:24:34Z

/usr/src/app/node_modules/whatsapp-web.js/src/authStrategies/LocalAuth.js:49
                    throw new Error(e);
                          ^

Error: Error: ENOTEMPTY: directory not empty, rmdir '/sessions/3080405618/Default'
    at /usr/src/app/node_modules/whatsapp-web.js/src/authStrategies/LocalAuth.js:49:27
    at async LocalAuth.logout (/usr/src/app/node_modules/whatsapp-web.js/src/authStrategies/LocalAuth.js:47:13)
    at async /usr/src/app/node_modules/whatsapp-web.js/src/Client.js:345:1

leandrosantoss · 2024-05-21T12:12:01Z

Delete message not working

Nodejs: 20
Chrome: 116~122

samuelfaj · 2024-05-21T13:10:35Z

/usr/src/app/node_modules/whatsapp-web.js/src/authStrategies/LocalAuth.js:49
                    throw new Error(e);
                          ^

Error: Error: ENOTEMPTY: directory not empty, rmdir '/sessions/3080405618/Default'
    at /usr/src/app/node_modules/whatsapp-web.js/src/authStrategies/LocalAuth.js:49:27
    at async LocalAuth.logout (/usr/src/app/node_modules/whatsapp-web.js/src/authStrategies/LocalAuth.js:47:13)
    at async /usr/src/app/node_modules/whatsapp-web.js/src/Client.js:345:1

Same started here.

rogerwh · 2024-05-24T14:11:07Z

Hello! I have problems connecting multiple devices using the pull request:

npm install github:pedroslopez/whatsapp-web.js#webpack-exodus

Some whatsapp devices connect correctly, but too many others dont work because they still on LOADING and stay in the PERCENTAGE (Loading Event)

Anybody have the same problem? I would like your help!

rogerwh · 2024-05-24T15:39:58Z

Even applying the exodus version, it continues to cause problems. We are unable to scan the qrcode. Sometimes it connects, but then the connection drop by NAVIGATION

Have you resolved this problem?

rogerwh · 2024-05-24T15:41:30Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.

Detailed info on versions: #2986

This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html

Hello, Have you resolved this problem?

wemersonrv · 2024-05-24T15:45:12Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986

This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html

Hello, Have you resolved this problem?

Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.

guigo613 · 2024-05-24T16:20:11Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.

For versions 2.24XX, you can use these repositories I put together.

I will provide the link to the repository and the issue that contains more details.

https://github.com/guigo613/alternative-wa-version
#3002

rogerwh · 2024-05-24T17:22:36Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.

Im not working with webCache, I dont have any problems with audio or message, but this happens on some clients while LOADING event :

LOADING SCREEN 99 WhatsApp
LOADING SCREEN 100 WhatsApp
LOADING SCREEN 100 WhatsApp
LOADING SCREEN 0 WhatsApp
LOADING SCREEN 10 WhatsApp
LOADING SCREEN 58 WhatsApp
LOADING SCREEN 58 WhatsApp
LOADING SCREEN 99 WhatsApp
LOADING SCREEN 0 WhatsApp

I dont know if there is a problem with WA 2.3000.XX

rogerwh · 2024-05-24T17:23:37Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.
For versions 2.24XX, you can use these repositories I put together.

I will provide the link to the repository and the issue that contains more details.

https://github.com/guigo613/alternative-wa-version #3002

This pull request dont work with WA 2.4XX, if use webCacheVersion WA throw an error on the browser, or there is something that im doing wrong?

wemersonrv · 2024-05-24T20:26:05Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.
For versions 2.24XX, you can use these repositories I put together.
I will provide the link to the repository and the issue that contains more details.
https://github.com/guigo613/alternative-wa-version #3002
Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.
For versions 2.24XX, you can use these repositories I put together.
I will provide the link to the repository and the issue that contains more details.
https://github.com/guigo613/alternative-wa-version #3002
This pull request dont work with WA 2.4XX, if use webCacheVersion WA throw an error on the browser, or there is something that im doing wrong?

This pull request dont work with WA 2.4XX, if use webCacheVersion WA throw an error on the browser, or there is something that im doing wrong?

I'm using this PR without cache and is everything fine for me. Using it with no cache forces the latest WA version (2.3000) and do not uses v2.24XX anymore.

guigo613 · 2024-05-24T21:36:57Z

Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.
For versions 2.24XX, you can use these repositories I put together.
I will provide the link to the repository and the issue that contains more details.
https://github.com/guigo613/alternative-wa-version #3002
Hello, ATM I can't connect Business accounts with this PR and WWEB >2.3, only normal whatsapp account. It hangs at 99% eternally and fails to finish. Tested both pairing code and qr code.
Detailed info on versions: #2986
This wwebversion works with both normal and business:

CACHED_WAWEB_VERSION_TO_USE=2.2412.50
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.50.html

Below version tested works with normal whatsapp but fails to connect whatsapp business account, always hangs on 100% and does not connect, both tried with pairing code and QRCode (and whatsapp business app was installed today 5 hours ago):

CACHED_WAWEB_VERSION_TO_USE=2.3000.1012750699
CACHE_TYPE=remote
REMOTE_PATH=https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.3000.1012750699-alpha.html
Hello, Have you resolved this problem?
Have you tried without webcache? Here some features don't works with webache yet... only when do not use it. Without cache everything works ok for now, even sending audio and video is ok and in the latest versions of 2.24XX it is not working.
For versions 2.24XX, you can use these repositories I put together.
I will provide the link to the repository and the issue that contains more details.
https://github.com/guigo613/alternative-wa-version #3002
This pull request dont work with WA 2.4XX, if use webCacheVersion WA throw an error on the browser, or there is something that im doing wrong?

This solution is to fix the video sending issue for versions 2.4XX. Unfortunately, I haven't adapted all the versions, but if there's a specific one you need, I can adapt it.

However, I don't know if this resolves your problem since it's not related to video sending but another issue. I don't know exactly what you're doing to determine if you're actually doing something wrong.

In the case of version 2.2412.50, it's not available there. I provided the link to the issue to show what it's about and how the people there addressed it. But again, this is only to solve the video sending problem for these versions, and in your case, it seems to be another issue.

* fix delete on 2.3000 * fix compareWwebVersions * fix: use proper comparison operator --------- Co-authored-by: alechkos <93551621+alechkos@users.noreply.github.com>

* Implement bot invoking capabilities * Update index.d.ts * Eslint

fix(webpack-exodus): Added the new patch

c1ae300

Eonus approved these changes Mar 15, 2024

View reviewed changes

PurpShell marked this pull request as draft March 16, 2024 15:25

maunklana mentioned this pull request Mar 19, 2024

Update Injected.js #2825

Closed

6 tasks

neb6la mentioned this pull request Mar 21, 2024

Dexie: Need to reopen db #2829

Closed

1 task

This comment was marked as off-topic.

Sign in to view

MoudiZd mentioned this pull request Mar 31, 2024

Text messages gives error #2857

Closed

1 task

PurpShell changed the title ~~Farewell, Webpack!~~ Farewell, Webpack! Also, patch for 2.24**!! Apr 2, 2024

fix(webpack-exodus): Fixed v2.3000.x and v2.24

db72385

PurpShell changed the title ~~Farewell, Webpack! Also, patch for 2.24**!!~~ Farewell, Webpack! Also, patch for 2.24xx.x!! Apr 3, 2024

PurpShell marked this pull request as ready for review April 3, 2024 00:53

chore(webpack-exodus): eslint

24196db

alechkos mentioned this pull request May 16, 2024

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default') | at __puppeteer_evaluation_script__:5:95 #3038

Closed

1 task

fixes

6df4eef

alechkos mentioned this pull request May 16, 2024

Client not connect #3039

Closed

1 task

alechkos mentioned this pull request May 17, 2024

Getting error after loading from session or scanning QR #3040

Closed

1 task

guyzyl mentioned this pull request May 18, 2024

Connecting whatsapp guyzyl/whatsapp-contact-sync#161

Closed

alechkos mentioned this pull request May 18, 2024

No longer working, what is happenning my friends? #3042

Closed

1 task

guyzyl mentioned this pull request May 19, 2024

Move to webpack-exodus of whatsapp-web.js guyzyl/whatsapp-contact-sync#164

Merged

Update LocalWebCache.js

1ecdc42

themazim mentioned this pull request May 22, 2024

Not able to scan QR code #3049

Closed

1 task

This comment has been minimized.

Sign in to view

fix delete on 2.3000 (#3048)

96b4742

* fix delete on 2.3000 * fix compareWwebVersions * fix: use proper comparison operator --------- Co-authored-by: alechkos <93551621+alechkos@users.noreply.github.com>

alechkos mentioned this pull request May 25, 2024

TypeError: Cannot read properties of null (reading '1'). Issue with webCache. #3053

Closed

1 task

Implement bot invoking capabilities (#3009)

bbb8d18

* Implement bot invoking capabilities * Update index.d.ts * Eslint

Farewell, Webpack! Re-injection, Pairing Code login, and 2.24x jumbofix #2816

Are you sure you want to change the base?

Farewell, Webpack! Re-injection, Pairing Code login, and 2.24x jumbofix #2816

Conversation

PurpShell commented Mar 14, 2024 • edited by alechkos

TL;DR:

PR Details

Description

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

Checklist

ricardoapaes commented Mar 14, 2024

complanboy2 commented Mar 14, 2024

Shinhwe commented Mar 15, 2024

PurpShell commented Mar 16, 2024

PurpShell commented Mar 16, 2024

voidpack commented Mar 17, 2024 • edited

MoudiZd commented Mar 17, 2024 • edited

complanboy2 commented Mar 17, 2024

MoudiZd commented Mar 17, 2024

complanboy2 commented Mar 17, 2024 • edited

voidpack commented Mar 17, 2024

mouhammad-zd commented Mar 17, 2024 • edited

voidpack commented Mar 17, 2024

MoudiZd commented Mar 17, 2024

maunklana commented Mar 18, 2024 • edited

voidpack commented Mar 18, 2024

maunklana commented Mar 18, 2024

voidpack commented Mar 18, 2024

This comment was marked as off-topic.

DenysSamoiliuk commented May 16, 2024 • edited

tofers commented May 17, 2024

TechnVision commented May 17, 2024

wildandahru commented May 19, 2024

tofers commented May 19, 2024

leandrosantoss commented May 21, 2024 • edited by alechkos

samuelfaj commented May 21, 2024

This comment has been minimized.

rogerwh commented May 24, 2024

rogerwh commented May 24, 2024

rogerwh commented May 24, 2024

wemersonrv commented May 24, 2024

guigo613 commented May 24, 2024

rogerwh commented May 24, 2024

rogerwh commented May 24, 2024

wemersonrv commented May 24, 2024

guigo613 commented May 24, 2024

PurpShell commented Mar 14, 2024 •

edited by alechkos

voidpack commented Mar 17, 2024 •

edited

MoudiZd commented Mar 17, 2024 •

edited

complanboy2 commented Mar 17, 2024 •

edited

mouhammad-zd commented Mar 17, 2024 •

edited

maunklana commented Mar 18, 2024 •

edited

DenysSamoiliuk commented May 16, 2024 •

edited

leandrosantoss commented May 21, 2024 •

edited by alechkos