How did you do it?
Getting the warning with latest Solar2d build, whatâs the deal here?
The latest admob plugin re-introduced this. Not the solar2d build.
Will try to release something tomorrow, but also this is just a warning last I checked not an error or anything with consequence
Maybe this is just a warning with no consequence, but given the wording of the warning (mention of possible âpolicy violationsâ) it seems prudent to adress it:
These versions have not been reviewed by Google Play. They could contain vulnerabilities or policy violations. Carefully evaluate any third-party SDKs before integrating them into your app.
I have seen a decline in downloads for all my apps over the last year. It would really suck if something like this was a negative signal to the ranking algorithm. If it isnât a big deal to fix, please do so.
Your app uses an outdated SDK version of androidx.fragment:fragment
This bug is still present in some of my android apps (with Solar2D 2025.3718). One of my apps that shows this bug in the Google Play console uses the following plugins for android:
plugin.pasteboard
CoronaProvider.native.popup.social
plugin.animation
plugin.google.iap.billing.v2
plugin.notifications.v2.firebase
[ UPDATE ]
Another one of my apps that doesnât show this warning uses:
CoronaProvider.native.popup.social
plugin.google.iap.billing.v2
plugin.notifications.v2
plugin.admob
So, logically, one of these is causing the warning:
plugin.pasteboard (dismissed)
plugin.animation - last updated: April 2020
plugin.notifications.v2.firebase ( Although, according to the documentation, itâs the same as plugin.notifications.v2
, it implements something extra for Firebase support.) - last updated: october 2024
UPDATE: itâs not Pasteboard plugin, another one of my app uses it and doesnât have the warning.
Hey @Scott_Harrison could you please check this comment. It seems the animation plugin is causing the warning about androidx.fragment:fragment.
I use all of those except for pasteboard and firebase, so probably one of those two.
I noticed that pasteboard got an update last month after a five-year break, so maybe try a new build and see if that fixed it?
Thank you, @colinmorgan. Regarding the pasteboard plugin update, I updated my app two days ago, and the warning is still pending.