feat: add new link with phone option #2363

fm1randa · 2023-07-27T03:38:39Z

Implement the new Whatsapp Web feature to link with phone number

Description

Added LinkingMethod.js - A class that will model the configuration object to choose to link with a QR code or phone number.

`index.js`

Added LinkingMethod.

`index.d.ts`

Deprecated qrMaxRetries.
Updated JSDoc for qr event.
Added JSDoc for the new code event and the new linkingMethod property.
Added LinkingMethod class

`src/Client.js`

Added logic to handle linkingMethod

`src/util/Constants.js`

Added CODE_RECEIVED event.

`tests/client.js`

Added 2 new test cases to cover linkingMethod paths.

Motivation and Context

Implement the new feature to link with phone number.

How Has This Been Tested

Tested running npm run shell and npm test. Some tests are failing, but I've confirmed that they're failing on the main branch too.

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).

tofers · 2023-07-27T13:42:29Z

The things that matter to me are.

Switching between the two in a running Puppeteer (without restarting the client) by number and back again
Entering a phone number after starting the client.
Changing the phone number (in case of its erroneous entry ).
Whether an error is handled after the codes waiting time expires

shirser121 · 2023-07-28T13:43:17Z

Thanks you !
If there is anything i can help, please write it down

fm1randa · 2023-07-28T21:34:32Z

The things that matter to me are.

Switching between the two in a running Puppeteer (without restarting the client) by number and back again

Entering a phone number after starting the client.

Changing the phone number (in case of its erroneous entry ).

Whether an error is handled after the codes waiting time expires

My approach differs from what you expect. It's not possible to switch between the two. Also, I think it wouldn't be a thing that most users will use. IMO, you usually want to avoid playing around authentication part while automating a Whatsapp session. You want to authenticate and make your automation online as soon as possible.
This library doesn't support user inputs after starting the client.
Same answer as the above subject. You can achieve a flexible way to change the phone number (I mean, without changing the source code) by using an environment variable for it.
I didn't reproduce this scenario locally. The expiration time is probably too big.

cc @tofers

tofers · 2023-08-01T13:50:55Z

Required to be reproduced as in the original WA.

QR
Transition to the phone
Switch to QR

These are the basic actions in the original Whatsapp.

Restarting the puppeteer to switch methods is not the best way.

fm1randa · 2023-08-01T18:01:41Z

Required to be reproduced as in the original WA.

QR

Transition to the phone

Switch to QR

These are the basic actions in the original Whatsapp.

Restarting the puppeteer to switch methods is not the best way.

@tofers Why would you like to switch methods in runtime? Just choose QR or Code, and then it will proceed with the selected mode.

without regen observer

jgarciach · 2023-08-02T20:06:13Z

just tested the phone code linking method and works great

lgtm

tuyuribr · 2023-08-04T19:33:47Z

Good work!

renzhxr · 2023-08-05T11:26:26Z

haven't been able to get the login code after being linked?

fm1randa · 2023-08-05T20:02:27Z

haven't been able to get the login code after being linked?

@renzhxr I'm not sure if I got your issue. Could you describe it better?

If I got your question correctly, the answer is: you won't get any code after linking.

andresayac

Tested good job

amiruldev20 · 2023-08-08T00:37:28Z

then how to do client.logout from this method?

pfnh26 · 2024-01-25T23:55:42Z

a funcionalidade é incrível, estou projetando um chatbot, mas sou muito novo em código e a biblioteca está me ajudando muito, recentemente criei minha lógica para essa funcionalidade mas acredito que houve alguma mudança no WhatsApp web e na funcionalidade parou, certo? Vou imprimir o erro: Error: No node found for selector: div[role="button"] > div > div at assert (C:\Users\Phelipe\Desktop\Sistema-whatsapp-web2\node_modules\whatsapp-web. js\node_modules\puppeteer\lib\cjs\puppeteer\common\assert.js:26:15) em DOMWorld.click (C:\Users\Phelipe\Desktop\Sistema-whatsapp-web2\node_modules\whatsapp-web.js\ node_modules\puppeteer\lib\cjs\puppeteer\common\DOMWorld.js:287:32) em process.processTicksAndRejections (node:internal/process/task_queues:95:5) em assíncrono handleLinkWithPhoneNumber (C:\Users\Phelipe\Desktop\ Sistema-whatsapp-web2\node_modules\whatsapp-web.js\src\Client.js:321:17) em async Client.initialize (C:\Users\Phelipe\Desktop\Sistema-whatsapp-web2\node_modules\whatsapp-web .js\src\Client.js:403:17) em startWhatsAppSession assíncrono (C:\Users\Phelipe\Desktop\Sistema-whatsapp-web2\server.js:1363:13) em assíncrono C:\Users\Phelipe\Desktop \Sistema-whatsapp-web2\server.js:935:7
If anyone can solve it, I would be very grateful
Até onde eu sei, não haverá mais suporte para esse recurso porque ele depende da tag HTML e está sujeito a erros como o que você está enfrentando neste exemplo.

I thought it was because of this: npm i https://github.com/pedroslopez/whatsapp-web.js#main
not working here, by the way there is a command that updates the entire library on your PC, because: npm install whatsapp-web.js It's not working here either

MobCode100 · 2024-01-26T00:48:16Z

Anyone can try it with npm install https://github.com/MobCode100/whatsapp-web.js.git and the below sample code:

const { Client, LinkingMethod, LocalAuth} = require('whatsapp-web.js');
const client = new Client(
    {
        linkingMethod:  new LinkingMethod({
            phone: {
                number: "+<COUNTRY CODE><PHONE NUMBER>"
            }
        }),
        puppeteer: {
            args: ['--no-sandbox'],
        },
    }
);
client.on('code', (code) => {
    console.log('CODE RECEIVED', code);
});
client.on('ready', () => {
    console.log('Client is ready!');
});
client.initialize();

@pfnh26 I've made a temporary modifications in my fork, that fixes the selector for me while waiting for this feature to be completed by this repository. Can I ask you to try and see if it works for you?

pfnh26 · 2024-01-26T01:56:16Z

Qualquer um pode experimentá-lo com npm install https://github.com/MobCode100/whatsapp-web.js.gito código de exemplo abaixo:
const { Client, LinkingMethod, LocalAuth} = require('whatsapp-web.js');
const client = new Client(
    {
        linkingMethod:  new LinkingMethod({
            phone: {
                number: "+<COUNTRY CODE><PHONE NUMBER>"
            }
        }),
        puppeteer: {
            args: ['--no-sandbox'],
        },
    }
);
client.on('code', (code) => {
    console.log('CODE RECEIVED', code);
});
client.on('ready', () => {
    console.log('Client is ready!');
});
client.initialize();
@pfnh26Fiz modificações temporárias em meu fork, que corrigem o seletor para mim enquanto aguardo que esse recurso seja concluído por este repositório. Posso pedir que você experimente e veja se funciona para você?

This change worked, but is it temporary?

Thank you very much, my project really appreciates it

MobCode100 · 2024-01-26T02:09:11Z

This change worked, but is it temporary?

Thank you very much, my project really appreciates it

Happy to have it working for you! It is temporary because WhatsApp Web can make changes on the UI, thus we'll have to update the code again. I'll keep maintaining my fork tho, cause one of my project is using it until whatsapp-web.js have the feature to link by phone.

pfnh26 · 2024-01-26T02:12:10Z

This change worked, but is it temporary?
Thank you very much, my project really appreciates it

Happy to have it working for you! It is temporary because WhatsApp Web can make changes on the UI thus, we'll have to update the code again. I'll keep maintaining my fork tho, cause one of my project is using it until whatsapp-web.js have the feature to link by phone.

Thanks again, but I'm hoping that whatsapp-web.js has this feature natively, we agree that QRcode authentication is very outdated

aidar87 · 2024-01-31T11:48:38Z

Any updates? will this pull request merged?

pfnh26 · 2024-04-02T19:49:27Z

Essa mudança funcionou, mas é temporária?
Muito obrigado, meu projeto realmente agradece

Fico feliz em tê-lo funcionando para você! É temporário porque o WhatsApp Web pode fazer alterações na UI, portanto teremos que atualizar o código novamente. Vou continuar mantendo meu fork, porque um dos meus projetos está usando-o até que o whatsapp-web.js tenha o recurso de link por telefone.

good afternoon my friend, how are you?
Again we are having the same problem when authenticating using a WhatsApp number, I believe that today WhatsApp made some changes as it also fell due to webVersionCache, but in the end, I would like to know if somehow I can learn to manipulate the code like you do so I can help you update this authentication method, if it's something manual, you can give me the tutorial and I'll make the updates, or if you can do it.
Thank you very much in advance

MobCode100 · 2024-04-02T20:03:28Z

Essa mudança funcionou, mas é temporária?
Muito obrigado, meu projeto realmente agradece

Fico feliz em tê-lo funcionando para você! É temporário porque o WhatsApp Web pode fazer alterações na UI, portanto teremos que atualizar o código novamente. Vou continuar mantendo meu fork, porque um dos meus projetos está usando-o até que o whatsapp-web.js tenha o recurso de link por telefone.

good afternoon my friend, how are you?
Again we are having the same problem when authenticating using a WhatsApp number, I believe that today WhatsApp made some changes as it also fell due to webVersionCache, but in the end, I would like to know if somehow I can learn to manipulate the code like you do so I can help you update this authentication method, if it's something manual, you can give me the tutorial and I'll make the updates, or if you can do it.
Thank you very much in advance

Thanks for the notice, I'll check the problem and try to fix it later this day. You can modify if you have some knowledge on JavaScript, there a lots of tutorial in the internet. The file to be modified is the LinkingMethod.js. Fork my git repo. Make your changes, and then install using the command above but be sure to replace the url to your forked git repo. Make sure to change the client headless config to false for testing changes. You can also modify the code directly inside node_modules folder for testing. Goodluck.

pfnh26 · 2024-04-02T20:08:37Z

Essa mudança funcionou, mas é temporária?
Muito obrigado, meu projeto realmente agradece

Fico feliz em tê-lo funcionando para você! É temporário porque o WhatsApp Web pode fazer alterações na UI, portanto teremos que atualizar o código novamente. Vou continuar mantendo meu fork, porque um dos meus projetos está usando-o até que o whatsapp-web.js tenha o recurso de link por telefone.

good afternoon my friend, how are you?
Again we are having the same problem when authenticating using a WhatsApp number, I believe that today WhatsApp made some changes as it also fell due to webVersionCache, but in the end, I would like to know if somehow I can learn to manipulate the code like you do so I can help you update this authentication method, if it's something manual, you can give me the tutorial and I'll make the updates, or if you can do it.
Thank you very much in advance

Thanks for the notice, I'll check the problem and try to fix it later this day. You can modify if you have some knowledge on JavaScript, there a lots of tutorial in the internet. The file to be modified is the LinkingMethod.js. Fork my git repo. Make your changes, and then install using the command above but be sure to replace the url to your forked git repo. Make sure to change the client headless config to false for testing changes. You can also modify the code directly inside node_modules folder for testing. Goodluck.

OK, I'll study this, I believe I can help you next time.
I'm looking for an investor so that I can launch this project, in addition to whatsapp-web.js I'm also using other libraries and Python to incorporate an AI model, soon I'll be able to hire people to help with this project, and these errors will no longer be problems ^^

MobCode100 · 2024-04-03T05:44:56Z

webVersionCache

I believe that today WhatsApp made some changes as it also fell due to webVersionCache,

Okay, so I've looked into it. It's an ongoing problem with WhatsApp Web version 2.3XXX. The workaround is to add the webVersionCache config as below:

const wwebVersion = '2.2412.54';
const client = new Client(
    {
        linkingMethod:  new LinkingMethod({
            phone: {
                number: "+<COUNTRY CODE><PHONE NUMBER>"
            }
        }),
        puppeteer: {
            args: ['--no-sandbox'],
        },
        webVersionCache: {
            type: 'remote',
            remotePath: `https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/${wwebVersion}.html`,
        },
    }
);

Be sure to update your whatsapp-web.js package with npm update.
See https://github.com/wppconnect-team/wa-version/tree/main/html for versions.

pfnh26 · 2024-04-03T10:34:27Z

webVersionCache

I believe that today WhatsApp made some changes as it also fell due to webVersionCache,

Okay, so I've looked into it. It's an ongoing problem with WhatsApp Web version 2.3XXX. The workaround is to add the webVersionCache config as below:
const wwebVersion = '2.2412.54';
const client = new Client(
    {
        linkingMethod:  new LinkingMethod({
            phone: {
                number: "+<COUNTRY CODE><PHONE NUMBER>"
            }
        }),
        puppeteer: {
            args: ['--no-sandbox'],
        },
        webVersionCache: {
            type: 'remote',
            remotePath: `https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/${wwebVersion}.html`,
        },
    }
);
Be sure to update your whatsapp-web.js package with npm update. See https://github.com/wppconnect-team/wa-version/tree/main/html for versions.

Sorry for not telling you how to resolve the webVersionCache error, below is the solution:
• In src/util/constants.js to replace:
webVersionCache: {
type: 'remote',
remotePath: 'https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2410.1.html',
}

It's the same thing you did, but including it this way you don't need to write it inside the client code.

MobCode100 · 2024-04-03T10:42:32Z

It's the same thing you did, but including it this way you don't need to write it inside the client code.

Thank you for this, I'll make this change soon!

pfnh26 · 2024-04-03T10:47:16Z

const wwebVersion = '2.2412.54';
const client = new Client(
    {
        linkingMethod:  new LinkingMethod({
            phone: {
                number: "+<COUNTRY CODE><PHONE NUMBER>"
            }
        }),
        puppeteer: {
            args: ['--no-sandbox'],
        },
        webVersionCache: {
            type: 'remote',
            remotePath: `https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/${wwebVersion}.html`,
        },
    }
);

Did you manage to resolve the "LinkingMethod" error?
Is it already operational?
I'm using it this way:
const { Client, LinkingMethod, LocalAuth} = require('whatsapp-web.js');
const client = new Client(
{
linkingMethod: new LinkingMethod({
phone: {
number: "+000000000"
}
}),
puppeteer: {
args: ['--no-sandbox'],
},
}
);
client.on('code', (code) => {
console.log('CODE RECEIVED', code);
});
client.on('ready', () => {
console.log('Client is ready!');
});
client.initialize();

MobCode100 · 2024-04-03T11:25:38Z

Is it already operational?

Yes, you can use it normally now. Just run npm update.

pfnh26 · 2024-04-03T12:43:33Z

Is it already operational?

Yes, you can use it normally now. Just run npm update.

The code is not being generated, could I be doing something wrong?

MobCode100 · 2024-04-03T14:47:20Z

The code is not being generated, could I be doing something wrong?

Try to delete your session folder, or maybe reinstall my repo:

npm uninstall whatsapp-web.js
npm install https://github.com/MobCode100/whatsapp-web.js.git

pfnh26 · 2024-04-03T15:46:17Z

The code is not being generated, could I be doing something wrong?

Try to delete your session folder, or maybe reinstall my repo:
npm uninstall whatsapp-web.js
npm install https://github.com/MobCode100/whatsapp-web.js.git

I did this, but the code is not generated, it does not give an error, but it also does not generate the code.
Is it the format of the WhatsApp number?

const { Client, LinkingMethod, LocalAuth} = require('whatsapp-web.js');
const client = new Client(
{
linkingMethod: new LinkingMethod({
phone: {
number: "+000000000000"
}
}),
puppeteer: {
args: ['--no-sandbox'],
},
}
);
client.on('code', (code) => {
console.log('CODE RECEIVED', code);
});
client.on('ready', () => {
console.log('Client is ready!');
});
client.initialize();

MobCode100 · 2024-04-03T19:25:15Z

Is it the format of the WhatsApp number?

I don't think so, I've tried exactly your code and I'm able to receive the code from WhatsApp. Maybe try new number? Just in case, I've changed the WhatsApp version in my repo. You can try to reinstall again.

pfnh26 · 2024-04-06T00:33:40Z

Is it the format of the WhatsApp number?

I don't think so, I've tried exactly your code and I'm able to receive the code from WhatsApp. Maybe try new number? Just in case, I've changed the WhatsApp version in my repo. You can try to reinstall again.

Sorry for the delay in testing, but it still doesn't work for me, the format I used before was like this <+556292286543>
my country changed the number by adding the number 9 after 62, like this
<+5562992286543> but this change was not necessary the first time the code worked, please if you can check why it is not working, when I request the code event it simply does not happen, nor does it give an error in my code

MobCode100 · 2024-04-06T18:43:53Z

<+5562992286543> but this change was not necessary the first time the code worked, please if you can check why it is not working,

I've tried that number, I still can get the code... very strange. Let's not spam our conversations here, create an issue here.

pfnh26 · 2024-04-08T11:42:00Z

<+5562992286543> but this change was not necessary the first time the code worked, please if you can check why it is not working,

I've tried that number, I still can get the code... very strange. Let's not spam our conversations here, create an issue here.

here it is :
MobCode100#1

PurpShell · 2024-04-14T01:59:56Z

#2816

pfnh26 · 2024-05-17T17:10:47Z

@MobCode100 all good?
Today the error was reported:
throw new Error('Evaluation failed: ' + (0, util_js_1.getExceptionMessage)(exceptionDetails));
^

Error: Evaluation failed: TypeError: Unable to read properties from undefined (reading 'push')
in fillModuleArray (evaluation in (:2:5), :6:74)

Updating this way I managed to solve:
npm install github:pedroslopez/whatsapp-web.js#webpack-exodus

You can update yours because of LinkingMethod:
npm install https://github.com/MobCode100/whatsapp-web.js.git

please?

MobCode100 · 2024-05-17T17:25:37Z

Does webpack exodus supports phone linking method?

pfnh26 · 2024-05-17T17:29:42Z

Does webpack exodus supports phone linking method?

unfortunately not

pfnh26 · 2024-05-18T20:46:09Z

@MobCode100
I made a small modification to the client instantiation by adding:
webVersionCache: {
type: "remote",
remotePath: "https://raw.githubusercontent.com/wppconnect-team/wa-version/main/html/2.2412.54.html"
}

the only problem is that apparently the webcache has a bug regarding sending MP4
using webpack-exodus and MP4 in this format works:
format = mp4
video Codec= libx264
video Bitrate = 500k'
audio bitrate = 128k

however with webpack-exodus the application may have a bug in other parts

fm1randa force-pushed the link-with-phone-number branch 2 times, most recently from c504d6f to b8f1488 Compare July 27, 2023 04:40

fm1randa marked this pull request as ready for review July 27, 2023 06:57

fm1randa added 11 commits August 1, 2023 15:04

feat: add new link with phone option

8bf71a3

without regen observer

feat: implement code regeneration observer

59e40e4

chore: revert .gitignore change

81a9b41

chore: .gitignore EOF

731c092

refactor: replace wrong LinkingOption param type with object

77b54f7

refactor: make qr handler use the new linkingMethod.qr.maxRetries

2a2e754

test: add new test cases for linking method

4cc2005

refactor: improve new code checking

d956766

test: replace number with a number provided in the .env

96d0266

refactor: improve constructor typing

032341e

refactor: make never properties optional

703c8c8

fm1randa force-pushed the link-with-phone-number branch from 6693f3b to 703c8c8 Compare August 1, 2023 18:06

tuyuribr added waiting for testers Waiting for other people test this PR in other envs good pr labels Aug 4, 2023

andresayac approved these changes Aug 7, 2023

View reviewed changes

Merge branch 'main' into link-with-phone-number

dd6fa05

alechkos mentioned this pull request Aug 8, 2023

Use phone number instead of scan qr code #1787

Open

1 task

PurpShell closed this Apr 14, 2024

PurpShell mentioned this pull request Apr 14, 2024

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

Open

6 tasks

alechkos removed a link to an issue May 12, 2024

How can we connect client through whatsapp number ? not using QR code. #2624

Closed

1 task

alechkos removed the waiting for testers Waiting for other people test this PR in other envs label May 12, 2024

feat: add new link with phone option #2363

feat: add new link with phone option #2363

Conversation

fm1randa commented Jul 27, 2023 • edited by alechkos

Implement the new Whatsapp Web feature to link with phone number

Description

index.js

index.d.ts

src/Client.js

src/util/Constants.js

tests/client.js

Motivation and Context

How Has This Been Tested

Types of changes

Checklist

tofers commented Jul 27, 2023

shirser121 commented Jul 28, 2023

fm1randa commented Jul 28, 2023

tofers commented Aug 1, 2023

fm1randa commented Aug 1, 2023

jgarciach commented Aug 2, 2023

tuyuribr commented Aug 4, 2023

renzhxr commented Aug 5, 2023

fm1randa commented Aug 5, 2023

andresayac left a comment

Choose a reason for hiding this comment

amiruldev20 commented Aug 8, 2023

pfnh26 commented Jan 25, 2024

MobCode100 commented Jan 26, 2024

pfnh26 commented Jan 26, 2024

MobCode100 commented Jan 26, 2024 • edited

pfnh26 commented Jan 26, 2024

aidar87 commented Jan 31, 2024

pfnh26 commented Apr 2, 2024

MobCode100 commented Apr 2, 2024

pfnh26 commented Apr 2, 2024

MobCode100 commented Apr 3, 2024 • edited

pfnh26 commented Apr 3, 2024

MobCode100 commented Apr 3, 2024

pfnh26 commented Apr 3, 2024

MobCode100 commented Apr 3, 2024

pfnh26 commented Apr 3, 2024 • edited

MobCode100 commented Apr 3, 2024

pfnh26 commented Apr 3, 2024 • edited

MobCode100 commented Apr 3, 2024

pfnh26 commented Apr 6, 2024

MobCode100 commented Apr 6, 2024

pfnh26 commented Apr 8, 2024

PurpShell commented Apr 14, 2024

pfnh26 commented May 17, 2024 • edited

MobCode100 commented May 17, 2024

pfnh26 commented May 17, 2024 • edited

pfnh26 commented May 18, 2024 • edited

fm1randa commented Jul 27, 2023 •

edited by alechkos

`index.js`

`index.d.ts`

`src/Client.js`

`src/util/Constants.js`

`tests/client.js`

MobCode100 commented Jan 26, 2024 •

edited

MobCode100 commented Apr 3, 2024 •

edited

pfnh26 commented Apr 3, 2024 •

edited

pfnh26 commented Apr 3, 2024 •

edited

pfnh26 commented May 17, 2024 •

edited

pfnh26 commented May 17, 2024 •

edited

pfnh26 commented May 18, 2024 •

edited