<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<base-config cleartextTrafficPermitted="true" />
</network-security-config>Hi Ziv Yves,
I found that this issue has not been solved yet.
I sometimes meet ERR_CLEARTEXT_NOT_ALLOWED when I tap the ads from Meta(Facebook).
How can I deal with this?
Regards,
Motohashi
Hi Junya,
Thank you for reaching out to us.
Can you provide us privately the following information below for us further check if this is still related to the previous thread you've referenced. You can provide the following details via Reply privately to author option or directly provide it to the link below.
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
Regards,
|
||||||
Hi Motohashi,
Thank you for providing the requested details.
Since this is specific to the mediation network of Meta(Facebook), can you confirm if the previous solution from the previous publisher doesn't solve the error you've encounter? If upon trying that still returns you this error, can you provide as a copy of a Charles log (see instruction here) privately capturing the error "ERR_CLEARTEXT_NOT_ALLOWED". You can provide the following details via Reply privately to author option or directly provide it to the link below.
Hi Pamela.
Thank you for your reply.
I confirmed that this solution could solve the error.
However, it enables app to allow all the http communications which can be a security hole.
> Since this is specific to the mediation network of Meta(Facebook),
OK, I would like to share this issue with Meta SDK Forum too.
Regards,
Motohashi
Hi Junya,
Thank you for confirming this. I've raised this to the wider team for the update in our documentation if there is a possible workaround for this error in the mediation network of Meta(Facebook). In the meantime, you can keep an eye on our release notes or blog for future updates regarding this.