QR Not authenticating and bug message

[randracar]

Describe the bug
When trying to authenticate, an error message appears, and the QR code appears after. But, the QR code does not work, and does not authenticate.
Steps to Reproduce
Steps to reproduce the behavior:
I could not find an way to reproduce it.

create() code
This is the code you use to create the client. e.g

const options = {
    sessionId: 'Imperial',
    headless: true,
    qrTimeout: 0,
    authTimeout: 0,
    restartOnCrash: start,
    cacheEnabled: false,
    useChrome: true,
    killProcessOnBrowserClose: true,
    throwErrorOnTosBlock: false,
    chromiumArgs: [
        '--no-sandbox',
        '--disable-setuid-sandbox',
        '--aggressive-cache-discard',
        '--disable-cache',
        '--disable-application-cache',
        '--disable-offline-load-stale-cache',
        '--disk-cache-size=0'
    ]
}

create(options)
    .then((client) => start(client))
    .catch((err) => new Error(err))

Expected behavior
I expected it to authenticate normally.

DEBUG INFO
This is the info printed to the console when you start your app. It should look like this

set -> e Error: Evaluation failed: TypeError: Cannot read property 'default' of undefined
    at window.<computed>.window.<computed> (/home/random-guy/.npm/_npx/6213/lib/node_modules/@open-wa/wa-automate/dist/lib/launch.js:1:36887)
    at __puppeteer_evaluation_script__:3:89
    at ExecutionContext._evaluateInternal (/home/random-guy/.npm/_npx/6213/lib/node_modules/@open-wa/wa-automate/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217:19)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Screenshots
If applicable, add screenshots to help explain your problem. Use headless: false to get screenshots

Host (please complete the following information):

• OS: Ubuntu 20.04

Additional context
Happens every time.

[smashah]

@randracar thanks for filling out the issue template, there is some information printed after the logo in the logs. can you add that here please, and actually include all the logs from the process. The system is also meant to take some screenshots. Please add those screenshots also.

thanks

[randracar]

@smashah , this is everything that appears.

The following appears on the logs folder:

This is what appears on the terminal.

[smashah]

duplicate: #1117

#1117 (comment)

[randracar]

@smashah I did what you said on how to resolve it, but it did not work. Same error message, same everything.

(Sorry if my english is bad)

[smashah]

@randracar can you try without all of those chromiumArgs please

[randracar]

@smashah Same error without them.

[smashah]

@randracar I will work on this tonight

[randracar]

@smashah Ok, thank you for your time helping me.

[JulioLongo]

Same problem herem, using ubuntu

[NasirKhalid24]

Running on ParrotOS linux and having the same issue - it started recently. Initially I would just keep re-starting the server and it would work eventually but now the issue is persistent

[smashah]

@NasirKhalid24 will be releasing a new version in a few minuets. stand by

[smashah]

@NasirKhalid24 @JulioLongo @randracar Can you please try the latest version:

https://github.com/open-wa/wa-automate-nodejs/releases/tag/3.1.9

and report back if this issue has been resolved.

Thanks

[NasirKhalid24]

@NasirKhalid24 @JulioLongo @randracar Can you please try the latest version:

https://github.com/open-wa/wa-automate-nodejs/releases/tag/3.1.9

and report back if this issue has been resolved.

Thanks

No longer having this issue - back to normal in the latest build. Thanks!

[smashah]

Closing thanks