I have upgraded Unity to version 6000.0.59f2 and rebuilt my application. After converting it to an AAB and submitting it to Google Play for review, it was immediately rejected. Please refer to my screenshot.
Here is what happened: previously, the AAB passed Google Play’s review after patching it with a patch tool. However, yesterday I submitted it directly without using the patch tool.
I compared the changes before and after patching and found that only the xrsdk-pre-init-library in libunity.so was modified to 8rsdk-pre-init-library .
I also confirmed that the version in the original libunity.so is 6000.0.59f2.
I would like to confirm whether version 6000.0.59f2 has already been fixed, or if I must use another version, as we are temporarily unable to upgrade the version.
Looking forward to your reply.
Yes, after being rejected, I used the patch tool, fixed the issue, resubmitted, and it was approved.
Since I have already upgraded Unity to 6000.0.59f2, I don’t want to perform patch fixes every time before submitting to Google Play.
With the help of Tautvydas-Zilys, it was identified that the Unity version in com.android.games.engine.build_fingerprint was still 6000.0.34f1 , as I had used a custom build but failed to update the Unity version in com.android.games.engine.build_fingerprint .
After making the necessary modifications, I resubmitted to Google Play, and the app passed the review.
I was able to solve the issue. It turns out it was an ID10T error. I am not the best at understanding the google play console’s messages and I didn’t realize when I was submitting the update to production access that it was also resubmitting an old closed testing version every time as well and that was what was causing the issue. The play console didn’t have any options for me to outright remove it it but hitting pause was enough for the production update to go through.
