-
-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wapi.js injected
several times
#2206
wapi.js injected
several times
#2206
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
1 similar comment
+1 |
@renandecarlo still having issues on Ubuntu 22.04, even after setting that version manually. Environment Puppeteer versions: Anyone? |
@sandro-salles you have to delete the tokens folder after editing the wpp version |
@renandecarlo already did that.. multiple times. no help... Using headless false, i can see that the instance is in fact authenticated: Bu the process hangs for some time as Waiting page load and then i can see some exceptions in the console: |
@sandro-salles i'm not sure then, maybe try an older version like const wppconnect = require('@wppconnect-team/wppconnect');
(async () => {
try {
wppconnect.defaultLogger.level = 'silly';
const client = await wppconnect.create({
session: 'wpp-session',
headless: false,
whatsappVersion: '2.3000.1013710920-alpha',
});
} catch(e) {
console.error('-> Não foi possível inicializar o Whatsapp Web', e);
}
})() |
+1 |
@Saifallak @sandro-salles @ademirMess if you want to say "plus 1" you can just react with a thumbs up. GitHub even hides repetitive replies. |
Hey, please test this PR: |
Description
It seems the current default wpp version 2.3000.1013232587-alpha causes the wapi.js to be injected several times at the first sync, leading to error in sent messages. After a restart, it works fine.
It seems to be fixed by updating the wpp version to newer versions, or using
whatsappVersion: null
ALSO: It seems wa-version is no longer generating main and beta wpp versions, just alpha ones
Environment
The text was updated successfully, but these errors were encountered: