Hello Developer @Magd Almuntaser

Thank you for the MPWA 13.0.0 update. I really appreciate the improvements that have been made, especially regarding the AI System Instruction, Campaign Queue fixes, and the LID-related fixes. Some of the requests I previously submitted have also been accommodated, and overall the system is running better now. 🙏

However, I found an issue in the Phonebook menu, specifically when using the “Fetch From Selected Device” feature.

The contacts retrieved from the device are not displayed in the normal phone number format (for example 628xxxxxxxxxx). Instead, they appear in a format like:

192024129056855@lid
25207716737179@lid
209371149688939@lid

Because of this, when the phonebook is used for campaign/blast, the sending process fails since the system considers those contacts invalid numbers.

Ideally, the contacts fetched from the device should still be stored or converted into the standard phone number format (62xxxxxxxxxx) so they can be used for broadcast or campaign purposes.

Could you please check whether this issue is related to the recent WhatsApp LID changes, or if the number conversion process is not working properly when importing contacts from the device?

Thank you in advance for your help and for continuously improving MPWA. 🙏

2 hours ago, Azhar Azziz said:

Does anyone have mirror of the update? My speed to download stuck on 10kbps.

You can try the update again now and the speed will be better.

1 hour ago, Shivendra Kr. Sahu said:

Thanks Dev..❤️

As of now in India, from March 1, 2026, this new rule has come into effect on WhatsApp that if anyone logs in to the web WhatsApp, it will be valid for 6 hours, after that it will be automatically logged out. What solution do you suggest for this?

Up to this moment, there is no solution.

1 hour ago, dentos said:

Hello Developer @Magd Almuntaser

Thank you for the MPWA 13.0.0 update. I really appreciate the improvements that have been made, especially regarding the AI System Instruction, Campaign Queue fixes, and the LID-related fixes. Some of the requests I previously submitted have also been accommodated, and overall the system is running better now. 🙏

However, I found an issue in the Phonebook menu, specifically when using the “Fetch From Selected Device” feature.

The contacts retrieved from the device are not displayed in the normal phone number format (for example 628xxxxxxxxxx). Instead, they appear in a format like:

192024129056855@lid
25207716737179@lid
209371149688939@lid

Because of this, when the phonebook is used for campaign/blast, the sending process fails since the system considers those contacts invalid numbers.

Ideally, the contacts fetched from the device should still be stored or converted into the standard phone number format (62xxxxxxxxxx) so they can be used for broadcast or campaign purposes.

Could you please check whether this issue is related to the recent WhatsApp LID changes, or if the number conversion process is not working properly when importing contacts from the device?

Thank you in advance for your help and for continuously improving MPWA. 🙏

Yes, I noticed that, it will be fixed urgently

31 minutes ago, Magd Almuntaser said:

You can try the update again now and the speed will be better.

Up to this moment, there is no solution.

Yes, I noticed that, it will be fixed urgently

Dns not resolved accessed from Central Java

Version 13.2.0 has been released

What's new in version 13.2.0:

- Added Delay For AI & Webhook.
- Fixed Images Buffer In Webhook & AI.
- Fixed PhoneNumber in Fetch Group.

40 minutes ago, Magd Almuntaser said:

Version 13.2.0 has been released

What's new in version 13.2.0:

- Added Delay For AI & Webhook.
- Fixed Images Buffer In Webhook & AI.
- Fixed PhoneNumber in Fetch Group.

makasi bang, ❤️ images buffer fix ❤️ otw update 13.2.0...

2 minutes ago, MD Raditya said:

oya bang tadi sewaktu update ke 13.0.0 ada update convert node libraries to ESM,
untuk server.js tidak terconvert kodenya, jadi harus ganti manual.

Yes, this problem is only for Indonesians because of Cloudflare.
My website is linked to Cloudflare, and Indonesia is experiencing difficulties this week with any website linked to Cloudflare, it's taking a very long time to load any file.

8 hours ago, Magd Almuntaser said:

Version 13.0.0 has been released

What's new in version 13.0.0:

- Added Image Inputs In Buttons & Lists Messages (Mandatory).
- Fixed List Message (AutoReply Page).
- Fixed Campaign Queue.
- Fixed System Instraction (AI).
- Fixed The LID Problem.
- Fixed Vulnerability In Laravel File Manager.
- Converted Node Libraries To ESM.
- Updated Api-Docs (Buttons & Lists).
- Updated Node Libraries.
- Updated Vendor Libraries.
- Updated AI Models List.

Thank you so much

48 minutes ago, Magd Almuntaser said:

Yes, this problem is only for Indonesians because of Cloudflare.
My website is linked to Cloudflare, and Indonesia is experiencing difficulties this week with any website linked to Cloudflare, it's taking a very long time to load any file.

🥲 13.2.0 ak jalanin manual bang migrate nya...

Apakah ada yang sudah mencoba autoreply? Di saya autoreply tidak bekerja

36 minutes ago, Azhar Azziz said:

Apakah ada yang sudah mencoba autoreply? Di saya autoreply tidak bekerja

sepertinya memang masih ada bug, jika di koneksi ulang akan berfungsi dan beberapa saat auto reply tidak merespon, punya saya juga demikian, jika ai diaktifkan dan apa bila ada yang ada update story maka ai akan merespon

16 minutes ago, pak kacung said:

sepertinya memang masih ada bug, jika di koneksi ulang akan berfungsi dan beberapa saat auto reply tidak merespon, punya saya juga demikian, jika ai diaktifkan dan apa bila ada yang ada update story maka ai akan merespon

Wah harus reconnect ya... Baiklah, nanti coba nunggu fix bug

MPWA has become very extensive, so I have reduced adding new features.
Continuous requests for additional features could harm MPWA reputation if it becomes overloaded with functionality and users start getting lost within it.

I considered adding OTP, I also thought about adding Flow, and I thought about adding automatic AI replies when there is no response.
However, I believe these features can be implemented through webhooks instead of adding them directly into MPWA, which would make the script too large and potentially confuse users.

Therefore, in my view, MPWA should remain as it is for now while focusing more on strengthening its security. I am also considering removing some features that previously existed but are no longer used. For example, themes will be removed in the next release, and the current theme will become the main and only theme.

Some pages will also be reorganized. For instance, the page for obtaining the API currently requires clicking on the profile picture, while it should have originally been placed in the left menu for easier access.

There is also the matter of Cron jobs. We previously created multiple cron jobs, even though Laravel already has an internal scheduler that should be used to run MPWA efficiently. In upcoming versions, the cron system will be integrated internally, and only the official Laravel cron command will be required in cPanel or aaPanel instead of multiple cron links.

Currently, multilingual support in MPWA relies on language files. In future versions, these will be moved to the database so that adding new texts becomes easier and so that version upgrades will not conflict with languages that users have previously customized.

At the moment, the files in MPWA are not well organized. In future releases, I plan to restructure the files, remove unnecessary code, and reduce their size.

For this reason, I would like to add new features based on your requests, but not at this time. Many of these requests do not directly benefit MPWA and may only serve a very small group of users. For now, the focus should be on improving the system, reducing the codebase, and organizing it properly so that future development becomes easier.

Imagine if MPWA had a (plugin system). Would you really need to upgrade the entire system every time? You would only need to click on the specific plugin from your dashboard and install it directly. This would keep MPWA lightweight, and each user could install only the plugins they actually need instead of having every feature included by default.

For example, on my own websites I only use MPWA to publish news to WhatsApp, which means I only use the send message feature. So why should I see a full frontend system, a user management system, a payment gateway system, and other components that I do not use?

A plugin system would solve this problem by allowing you to install only what you need, while also enabling other developers to build their own plugins.

Therefore, it would be better to postpone feature requests until a later time.

1 hour ago, Magd Almuntaser said:

MPWA has become very extensive, so I have reduced adding new features.
Continuous requests for additional features could harm MPWA reputation if it becomes overloaded with functionality and users start getting lost within it.

I considered adding OTP, I also thought about adding Flow, and I thought about adding automatic AI replies when there is no response.
However, I believe these features can be implemented through webhooks instead of adding them directly into MPWA, which would make the script too large and potentially confuse users.

Therefore, in my view, MPWA should remain as it is for now while focusing more on strengthening its security. I am also considering removing some features that previously existed but are no longer used. For example, themes will be removed in the next release, and the current theme will become the main and only theme.

Some pages will also be reorganized. For instance, the page for obtaining the API currently requires clicking on the profile picture, while it should have originally been placed in the left menu for easier access.

There is also the matter of Cron jobs. We previously created multiple cron jobs, even though Laravel already has an internal scheduler that should be used to run MPWA efficiently. In upcoming versions, the cron system will be integrated internally, and only the official Laravel cron command will be required in cPanel or aaPanel instead of multiple cron links.

Currently, multilingual support in MPWA relies on language files. In future versions, these will be moved to the database so that adding new texts becomes easier and so that version upgrades will not conflict with languages that users have previously customized.

At the moment, the files in MPWA are not well organized. In future releases, I plan to restructure the files, remove unnecessary code, and reduce their size.

For this reason, I would like to add new features based on your requests, but not at this time. Many of these requests do not directly benefit MPWA and may only serve a very small group of users. For now, the focus should be on improving the system, reducing the codebase, and organizing it properly so that future development becomes easier.

Imagine if MPWA had a (plugin system). Would you really need to upgrade the entire system every time? You would only need to click on the specific plugin from your dashboard and install it directly. This would keep MPWA lightweight, and each user could install only the plugins they actually need instead of having every feature included by default.

For example, on my own websites I only use MPWA to publish news to WhatsApp, which means I only use the send message feature. So why should I see a full frontend system, a user management system, a payment gateway system, and other components that I do not use?

A plugin system would solve this problem by allowing you to install only what you need, while also enabling other developers to build their own plugins.

Therefore, it would be better to postpone feature requests until a later time.

@Magd Almuntaser

Thanks mate, I really appreciate your effort in maintaining this project. I just have a quick question. Will it work if I do a fresh package.json installation (node_modules) and install the Composer dependencies again?

2 minutes ago, Licenship said:

@Magd Almuntaser

Thanks mate, I really appreciate your effort in maintaining this project. I just have a quick question. Will it work if I do a fresh package.json installation (node_modules) and install the Composer dependencies again?

Yes working ..

24 minutes ago, Magd Almuntaser said:

Yes working ..

Thanks. Is there any solution for the issue where sending a button message through the website interface works, but a blank message is sent first before the actual message?

hi @Magd Almuntaser thanks for update.
in list message media select button not working.
add api to send template message.
add api to add phone number in phone book.

56 minutes ago, Licenship said:

Thanks. Is there any solution for the issue where sending a button message through the website interface works, but a blank message is sent first before the actual message?

There is no solution because this is actually the solution for sending a button message, and without it the service will not work because it is an exclusive paid service for WhatsApp. In this way we trick WhatsApp into thinking that we sent an empty message, but in reality it is a button outside the frame, so an empty message should appear at the top.

49 minutes ago, Sachin Dadhaniya said:

hi @Magd Almuntaser thanks for update.
in list message media select button not working.
add api to send template message.
add api to add phone number in phone book.

1- it's working on v13.2.0 .. so just update your version
2- soon.
3- soon.

troubleshoot not working. 500 Server Error
live chat not working. 500 Server Error
How can I fix this?

Edited March 7Mar 7 by anadarshh88

Version 13.0.0 is better than version 13.2.0 for me.

• I downgraded to version 13.0.0

• bufferedimage works

• there are no repeating webhooks like in version 13.2.0

1 hour ago, MD Raditya said:

Versi 13.0.0 lebih baik daripada versi 13.2.0 menurut saya.

• Saya menurunkan versi ke versi 13.0.0

• bufferedimage berfungsi

• tidak ada webhook berulang seperti pada versi 13.2.0

V13.2.0 ini perbaikan dari v13.0.0, bagaimana anda mengatakan malah lebih baik v13.0.0?, jangan melihat daribsatu sisi saja....

17 minutes ago, John Tralala said:

V13.2.0 ini perbaikan dari v13.0.0, bagaimana anda mengatakan malah lebih baik v13.0.0?, jangan melihat daribsatu sisi saja....

😁untuk kebutuhan saya, yo untuk anda bebas pilih versi mana, karena saya menggunakan n8n, untuk versi 13.2.0 terdapat looping yg agak menggangu, ya memang bisa menggunakan filter. Tetapi untuk kebutuhan saya, saya lebih suka menggunakan versi 13.0.0 yang sama sekali tidak adanya looping.

1 hour ago, MD Raditya said:

Version 13.0.0 is better than version 13.2.0 for me.

• I downgraded to version 13.0.0

• bufferedimage works

• there are no repeating webhooks like in version 13.2.0

What are you talking about?
Do you know that in version 13.2.0 only one word was modified?
As for what was written in the features, I wrote it in 13.2.0 because I forgot to include it in 13.0.0. It was already present in 13.0.0,
On 13.2.0 I only changed one word. Instead of:

bufferImage
I made it:
Imagebuffer

So I wrote in the features what I forgot to mention in version v13.0.0

@Magd Almuntaser troubleshoot not working. 500 Server Error
live chat not working. 500 Server Error
How can I fix this?

26 minutes ago, anadarshh88 said:

@Magd Almuntaser troubleshoot not working. 500 Server Error
live chat not working. 500 Server Error
How can I fix this?

The two files are missing because of your antivirus software, these files are encrypted, so the antivirus removed them.

Tidak bisa menambahkan auto reply