TypeError: P.PHOTO_PICKER_QUALIFIED_EMOJIS is not iterable

[yuzedong]

Description

I imported wa.js in my Chrome extension. When a user clicks on the three-dot button in the top right corner of a group chat in web.whatsapp.com, the group info does not show up and an error is reported in the console. The error is as follows:

TypeError: P.PHOTO_PICKER_QUALIFIED_EMOJIS is not iterable
at t.default (lazy_loaded_low_priority_components.2eb74f3a79d43c7a730d.js:2:295311)
at wa (vendor1app.93f2846fd0de96e2ec08.js:30:62964)
at _u (vendor1app.93f2846fd0de96e2ec08.js:30:120158)
at vl (vendor1app.93f2846fd0de96e2ec08.js:30:109100)
at pl (vendor1app.93f2846fd0de96e2ec08.js:30:109028)
at hl (vendor1app.93f2846fd0de96e2ec08.js:30:108891)
at nl (vendor1app.93f2846fd0de96e2ec08.js:30:105698)
at ol (vendor1app.93f2846fd0de96e2ec08.js:30:106087)
at Fi (vendor1app.93f2846fd0de96e2ec08.js:30:46805)
at vendor1~app.93f2846fd0de96e2ec08.js:30:103606

Environment

• **WA-JS version(s): 2.23.3
• Browser: Chrome 111
• OS: Windows X / OSX

Steps to Reproduce

1. Inject wppconnect-wa.js.
2. Click on a specific group on web.whatsapp.com.
3. Click on the More (three-dot) icon at the top right corner and select the first group info option.
4. An error is reported in the console.

Add any other context about the problem here. If applicable, add screenshots to help explain.

[yuzedong]

Please take a look for me, and thank you very much!

[edgardmessias]

@yuzedong what is the WhatsApp version?

[yuzedong]

2.2316.6

[luiscuriel]

Same problem here! Any solution? Thanks!

[luiscuriel]

I fixed it by injecting the js later, after authentication is ok.

[edgardmessias]

Thanks @luiscuriel , I will try to reproduce it on my machine and try to figure out a way to avoid this

[yuzedong]

Thanks @luiscuriel , I will try to reproduce it on my machine and try to figure out a way to avoid this

When can this issue be fixed? tks.

[luiscuriel]

It is still happening on some sessions for me...

[yuzedong]

Ok, Please fix it as soon as possible. Thanks!

[yuzedong]

I'm using the latest version 2.24.0, and the process remains the same as before. The previous console error has disappeared, but a new error has occurred. The error is as follows: