Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fyber Adapter SDK com.applovin.mediation:fyber-adapter seems not to be CMP compliant #81

Open
spielepalast opened this issue Jan 14, 2025 · 3 comments

Comments

@spielepalast
Copy link

Your app, including any SDKs used, must abide by a user’s preferences regarding usage of the Android advertising identifier, specifically respecting their ”Opt out of Interest-based Advertising” or ”Opt out of Ads Personalization” setting.
Your app may face additional enforcement actions, if you do not resolve this issue by February 11, 2025.
Issue details
We found an issue in the following area(s):

Version code 2011305:
SDK: Fyber Adapter SDK com.applovin.mediation:fyber-adapter
To bring your app into compliance, follow these steps:

Fyber Adapter SDK com.applovin.mediation:fyber-adapter: Consider upgrading to a policy-compliant version of the SDK if available from your SDK provider, or removing the SDK.

Expected behaviour

should be CMP compliant

Actual behaviour

seems not to be CMP compliant

Environment
  • AIR SDK version:
  • Device OS:
  • Device version:
  • Development IDE:
  • Development OS:
Logs

Device logs if relevant

@spielepalast
Copy link
Author

I have also contacted digitalturbine (fyber) and they responded:

Thank you for reaching out. We are aware of the issue and we are working on a fix. Appreciate your patience with us.

@spielepalast
Copy link
Author

Updated response from digitalturbine (fyber)

We want to give you a quick update on a recent SDK issue related to Google Play Ads Policy compliance.

As Google frequently updates its ad policies, the way an SDK works with Advertising ID values needs periodic adjustments to remain compliant. Immediately after identifying the issue, our Product and Engineering team have been working on a fix to update the logic of how we collect and process these values.

We are happy to confirm that the updated SDK version with the new logic is already in QA. We also released it on our O&O app and have already received confirmation directly from the Google team that it resolved the issue.

We aim to release the SDK fix, version 8.3.5, to all DT Exchange publishers within the next 24 hours, pending thorough tests and investigation with Google and our mediation partners, including MAX, LevelPlay, and AdMob. I will let you know immediately when the SDK version is available for you to update.

@marchbold
Copy link
Contributor

Thanks, we'll keep an eye out for the update, but please let us know if they inform you of the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants