We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Yesterday morning I found that my whatsapp instance not auth
In my logs info:
2022-06-21T04:07:09+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'SYNCING', info: 'SYNCING' } 2022-06-21T04:07:09+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'SYNCING', info: 'SYNCING' } 2022-06-21T04:07:20+07:00 info: [whatsappsession:client] WA-JS version: 2.7.3 2022-06-21T04:07:20+07:00 state changed: UNLAUNCHED 2022-06-21T04:07:20+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'SYNCING', info: 'NORMAL' } 2022-06-21T04:07:21+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'QR', info: 'OPENING' } 2022-06-21T04:07:21+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'QR', info: 'OPENING' } 2022-06-21T04:07:21+07:00 state changed: OPENING 2022-06-21T04:07:22+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'QR', info: 'PAIRING' } 2022-06-21T04:07:22+07:00 state changed: PAIRING 2022-06-21T04:07:22+07:00 interface changed { displayInfo: 'CONNECTING', mode: 'QR', info: 'NORMAL' } 2022-06-21T04:07:22+07:00 state changed: UNPAIRED
is it do by signal from whatsapp to re-auth whatsapp? my phone with whatsapp app always online and charged
The text was updated successfully, but these errors were encountered:
it's like #784 ?
Sorry, something went wrong.
having same problem
Did this problem fixed?
8ec5264
No branches or pull requests
Yesterday morning I found that my whatsapp instance not auth
In my logs info:
is it do by signal from whatsapp to re-auth whatsapp? my phone with whatsapp app always online and charged
Environment
The text was updated successfully, but these errors were encountered: