H have this issue when sending template message the template is approved and parameters are correct but I don't know why doesn't work, only the hello_world template works fine
{"error":{ "message":"(#135000) Generic user error", "type":"OAuthException", "code":135000," error_data":{ "messaging_product":"whatsapp", "details":"Generic user error" }, "fbtrace_id":"AChsM9L4vSRF3_71gmezn5O" }}

I’m encountering an issue with app-ads.txt verification in Google AdMob. I selected 'Verify App' in 'App Verification'. Despite following all the steps and confirming that the file is properly set up, I keep getting the error: "We couldn't verify", along with the following message from Google AdMob:

"Your details don't match the information in your AdMob account."

Here’s what I’ve done so far:

app-ads.txt File Accessibility:

The app-ads.txt file is hosted at:

• http://theiafintech.com/app-ads.txt

• theiafintech.com/app-ads.txt

Visiting either of these links returns the app-ads.txt content successfully. I validated the file’s format using adstxt.guru, and it states that the file is formatted correctly.

Developer Website and App Store Integration: The app is published on the Apple App Store, and clicking the 'App Support' link from the app listing successfully navigates to the company website: https://www.theiafintech.com/

Guide Reviewed: I’ve carefully reviewed the AdMob instructions here. Everything appears to match the requirements, as the file is publicly accessible on both HTTP and HTTPS formats.

Issue: Despite the above, Google AdMob is unable to verify the app-ads.txt file, and I continually get the error message "We couldn't verify."

Request: Could someone help identify what might be going wrong? Are there additional steps or requirements (beyond those outlined in the guide) that I might be missing? I’d really appreciate any insights or suggestions.

Thank you for your help!

FYI: Here’s what I get after selecting 'Verify App':

Button and flow messages sent via WhatsApp Business API are sent to most customers, some of whom receive a 131026 non-delivery notice. In controls; -Numbers are valid WhatsApp numbers -Current WhatsApp installed -Current WhatsApp service agreement appears to be approved. We could not understand why the sent messages could not be sent to some customers.

I'm using the WhatsApp Cloud API to send images with the view_once flag, but the image is still accessible multiple times, even though I have set the view_once parameter in the API request. I have followed the documentation carefully, and while uploading the media, I included the view_once flag. However, when sending the media through the media ID, the "view once" functionality doesn't seem to work as expected.
Upload Request: json Copy code { "file": "", "type": "image", "view_once": true } Send Request: json Copy code { "messaging_product": "whatsapp", "to": "918891168586", "type": "image", "image": { "id": "912099421100415" }, "view_once": true }
Despite following this process, the image is still viewable multiple times by the recipient.
Could you please confirm:
Is the view_once feature fully supported for images sent via media ID in the WhatsApp Cloud API? Are there any specific API versions, account settings, or additional configurations required to enable this functionality? Is there a known issue with the view_once flag, or is it still being rolled out for certain users? I appreciate your help and guidance in resolving this issue.
Thank you!

Hi there! We've been using Meta Pixel for a long time, we use it transmit our events to FB Pixel using official FB library for java However, 2 days we started to receive error during sending events to Pixel It returns HTML page saying "We're working on it and we'll get it fixed as soon as we can "(attached below). But it's been more than 2 days, all FB SDK tool statuses are green we noticed that only around 1% of our events fail.
Do you know what's the reason? Where I can check the Meta Pixel status? Thanks
com.facebook.ads.sdk.APIException$FailedRequestException:
Facebook | Error
Sorry, something went wrong.
We're working on it and we'll get it fixed as soon as we can.
Go Back
Facebook © 2024 · Help Center