The AAB compiled with Unity 6000.0.58f2 still has issues when submitted to the Google Play Store

Q&A for CVE-2025-59489
,
1

Hi,

I upgraded the project to Unity 600000.58f2, and after fixing the errors caused by the upgrade, I generated an AAB file and submitted it to Google Play.

However, even after the review was approved, the issue still hasn’t been resolved.

Did I do something wrong?

pic1
pic1503×343 15.6 KB

pic2
pic21181×414 35.2 KB

2

I am having the same issue too!

Perhaps it’s related to the plugins I’m using?

  • Unity 2022.3.62f2
  • In App Purchasing 4.13.0
  • Advertisement Legacy 4.12.0
  • Google In App Review
  • AppLovin MAX with various integrations

[EDIT]
Oh, looks like the warning went away! Maybe Google was a bit delayed detecting the patch.

3

I’m experiencing the same issue. I think we should wait a while; there might be a delay in updating the compliance status.

4

I’m experiencing the same problem. My game was originally developed in Unity 2021.3, and I upgraded to Unity 6000.055f1, but the warning persists after the upgrade.

5

Yeah I was stuck on that issue too, You have to go back and redo the questionnaires about data collections and such.

6

Can you double check the version you updated to? 6000.0.55f1 does not have the fix.

7

You need to update all your tracks with the patched version - it usually takes a few hours for the violation to go away.
I.e. if you have a version in Internal Testing / Open Beta / Closed Beta etc. you need to push it to all channels, or close channels you are not using anymore