the qrcode loader is undefined when the session was previously created
Can you give me steps to recreate and the actual problem? If the sessions was already created does it continuously load for you? Whatsapp might changed their detection.
Actually I think whatsapp has changed the mode of detection. when the section is created for the first time and everything is ok.
but at the second launches its loop at the level on the loading of the qrcode
On Nov 8 2019, at 4:00 pm, S.M.A.Sh notifications@github.com wrote:
Can you give me steps to recreate and the actual problem? If the sessions was already created does it continuously load for you? Whatsapp might changed their detection.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://link.getmailspring.com/link/[email protected]/0?redirect=https%3A%2F%2Fgithub.com%2Fsmashah%2Fsulla%2Fissues%2F9%3Femail_source%3Dnotifications%26email_token%3DAEXCYYHCDIY4OPWZMLRWGODQSV5J7A5CNFSM4JKXRHR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDSLWOY%23issuecomment-551861051&recipient=cmVwbHkrQUVYQ1lZREZCSDNDN0NZR1NPVFpRS1YzMksyWjdFVkJOSEhCNTdYNkNNQHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe (https://link.getmailspring.com/link/[email protected]/1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEXCYYGT5LQDSEUCYLAFBSTQSV5J7ANCNFSM4JKXRHRQ&recipient=cmVwbHkrQUVYQ1lZREZCSDNDN0NZR1NPVFpRS1YzMksyWjdFVkJOSEhCNTdYNkNNQHJlcGx5LmdpdGh1Yi5jb20%3D).

I think this condition has changed

I think WhatsApp has blocked our user-agent. I'll make an update where users can set the user agent themselves in order to have some sort of variation between users of this lib.
Great idea.
@gildastema https://github.com/smashah/sulla#custom-set-up
v.1.2.6
Give it a whirl let me know if it works out for you thanks.
The QR is not being shown on the console.

Any idea what might be wrong?
I see that you have a new ev.on("qr"... Do I have to use it to print the QR to the console?
@rubenfaria Can you please show me your code. Also, try deleting the sessions folder and try again.
Sure thing!

It's just the starter example. I wanted to test whether the session would be saved.
PS. You're the man! This repo of yours has the best care for sure.
@gildastema https://github.com/smashah/sulla#custom-set-up
v.1.2.6
Give it a whirl let me know if it works out for you thanks.
Let me check and come back to you
@gildastema https://github.com/smashah/sulla#custom-set-up
v.1.2.6
Give it a whirl let me know if it works out for you thanks.Let me check and come back to you

The problem is different with the initialization on loop on the loading of the qrcode
I'm going to try to set up the hardcoded user agent to that of WhatsApp web desktop client itself. Let's see what they do with that.
@gildastema @rubenfaria it looks like it works if you make the user agent the same as a whatsapp web desktop electron client one. You can find others here:
https://developers.whatismybrowser.com/useragents/explore/software_name/whatsapp/?order_by=-software_version
e.g
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) WhatsApp-Rebellin/1.0 Chrome/53.0.2785.143 Electron/1.4.15 Safari/537.36
I'll push a new version of sulla-hotfix with this new user agent.
Am I missing something?
The QR appears on Sulla but no on Hotfix.

@rubenfaria can you confirm you:
@rubenfaria can you confirm you:
1. Are using latest version. 2. Deleted the sessions folder before trying 3. Tried without the custom parameters and see if it works (I'm pretty sure if you change user-agents while still using the same session folder it will fail)
Yes to all three. I had a collegue and myself to start two different brand new projects from scratch and the outcome was the same.
I'm really lost about what's happening. Sulla works with the problem of having to delete the session folder at restart.
@rubenfaria can you screenshot what you see when you do headless:false and what environments are you running on?
@rubenfaria can you screenshot what you see when you do headless:false and what environments are you running on?
Thanks for your time, man.
Microsoft Windows [Version 10.0.17134.950]
node v12.13.0
npm: 6.12.0

It also opens up WhatsApp Web at Chromium.
@rubenfaria what does chromium show?
I'm having the same problem as @rubenfaria
@rubenfaria can you screenshot what you see when you do headless:false and what environments are you running on?

Looks like both of you are running windows. I'm on mac right now, can you try using a custom user agent (use your own by googling 'whats my user agent') and try that way.
@rubenfaria what does chromium show?

Looks like both of you are running windows. I'm on mac right now, can you try using a custom user agent (use your own by googling 'whats my user agent') and try that way.
Same thing as before.

It must be a Windows thing.
I deployed the same sample project usin a custom user agent to Heroku and it ran just fine.
"session",
{ headless: true },
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3882.0 Safari/537.36"

I guess it messes up because you have a safari user agent on a Windows device. Try locally without the safari at the end or just use your own user agent as I described above.
I guess it messes up because you have a safari user agent on a Windows device. Try locally without the safari at the end or just use your own user agent as I described above.
I did. That one above I got from Chromium. I also tried Mozilla's, Edge's and Chrome's. For now I'm gonna work on this project using Linux. I'll get back to you telling whether everything went well in there. Thanks for your help.
I'm going to close this issue for now, thanks.
Most helpful comment
I did. That one above I got from Chromium. I also tried Mozilla's, Edge's and Chrome's. For now I'm gonna work on this project using Linux. I'll get back to you telling whether everything went well in there. Thanks for your help.