Baileys
Baileys copied to clipboard
WhiskeySockets
[BUG] buttons and lists stopped working
Yes, after the latest update on Android today, list and button messages didn't show up on the receiver.
Same with me any Solution ?
No solution for now, but to appear on wa web you can still add the viewOnce parameter
it's a sign that it's time for you to change lib:v hehehe
It's not about this lib, but indeed at this time WhatsApp has an update and some are missing, I tried other libs and got the same thing, it's good that we try to solve this problem together
It's not about this lib, but indeed at this time WhatsApp has an update and some are missing, I tried other libs and got the same thing, it's good that we try to solve this problem together
right bro the problem is not in the lib... there may be an update on the whatsapp server not on the client
I have just checked that now i am not getting response to list messages from the bank who are using official api. Seems this bug is temporary.
I have just checked that now i am not getting response to list messages from the bank who are using official api. Seems this bug is temporary.
wati working /:
I have just checked that now i am not getting response to list messages from the bank who are using official api. Seems this bug is temporary.
btw this using official API. work mobile and web
I have just checked that now i am not getting response to list messages from the bank who are using official api. Seems this bug is temporary.
btw this using official API. work mobile and web
api kok ditanya
I have just checked that now i am not getting response to list messages from the bank who are using official api. Seems this bug is temporary.
api kok ditanya
kamu hengker yah
FYI, the maintainer have decided to put button feature as deprecated feature. The deprecation will be done in the future. This means the button will not be fixed anymore. It's time to say goodbye to the button feature from the library.
After 5 votes from Contributors, Mods, and even Pedro himself, I've decided to begin the process of deleting Buttons and Lists. The patch that I released a few days ago was either under wraps or not widely applied for a long time (2 months) and the same day I posted it here it has been patched internally by WhatsApp. This timing is very fishy and to not irritate Meta even more, I drew this line. If you're a business, and you profit a lot from every conversion you make, you can go ahead and use the official Meta API for all I care. I've been working discreetly with other library leaders for about 50 hours total all together reverse engineering to figure this out (whatsmeowlead, whatsappweb4j, baileys, openwa and wppconnect) and after all our efforts nothing has worked out. This is what we really end up with in the end because depending on solution after solution whatever you build on top of it will fail. Like building a hospital on bamboo scaffolding. It takes a heavy heart to say this, I know. I also have a mountain of code to change now (Hypere, StormChat, and countless other partners and clients over the years). Open-wa, Baileys, whatsapp-web.js, and wppconnect will be deprecated keys. The process is slightly different for each library but in the end it will all be the same. - purpshell, maintainer of whatsapp-web.js and Baileys for 3 years now (in case you didn't know)
2, 2228, 8
Not work on ios Im worked on Ios and Web using "version": [2, 2228, 8]
In IOS Still working
So I'm gonna have a look today. Still even if i fix it, at this point you really shouldn't be relying on buttons.
Same with me any Solution ?
No solution for now, but to appear on wa web you can still add the viewOnce parameter
yeah, the button can still be seen on your 'whatsapp web' but it's not sent to your mobile device... this issue hasn't been fixed for so long
After 5 votes from Contributors, Mods, and even Pedro himself, I've decided to begin the process of deleting Buttons and Lists. The patch that I released a few days ago was either under wraps or not widely applied for a long time (2 months) and the same day I posted it here it has been patched internally by WhatsApp. This timing is very fishy and to not irritate Meta even more, I drew this line. If you're a business, and you profit a lot from every conversion you make, you can go ahead and use the official Meta API for all I care. I've been working discreetly with other library leaders for about 50 hours total all together reverse engineering to figure this out (whatsmeowlead, whatsappweb4j, baileys, openwa and wppconnect) and after all our efforts nothing has worked out. This is what we really end up with in the end because depending on solution after solution whatever you build on top of it will fail. Like building a hospital on bamboo scaffolding. It takes a heavy heart to say this, I know. I also have a mountain of code to change now (Hypere, StormChat, and countless other partners and clients over the years). Open-wa, Baileys, whatsapp-web.js, and wppconnect will be deprecated keys. The process is slightly different for each library but in the end it will all be the same. - purpshell, maintainer of whatsapp-web.js and Baileys for 3 years now (in case you didn't know)
hi @arskyy and teams, thanks for everything that you guys have done until this far. may i know, other than button and list, what else that dev will deprecate (other than on server side)? just precautions. thanks
I forgot to reply, but there's a server side filter now. So the issue cannot be solved. Btw only buttons, list and template are getting deprecated
I forgot to be reply, but there's a server side filter now. So the issue cannot be solved. Btw only buttons, list and template are getting deprecated
thanks @Auties00 for clarifications.
It seems that if we downgrade the library version, the message button will work again, right?
It seems that if we downgrade the library version, the message button will work again, right?
on older(2 Months ago) versions of Whatsapp yes