Successfully Patched aab But Cannot Publish due to 16KB memory page size Error

My game was originally submitted to Google Play after being built with Unity 2022.3.f1, Target SDK 33. I patched it with the Tool and uploaded it to the Play Console.

However, I get an error that the game doesn’t support 16KB memory page size, so I can’t publish it.

Is there a way to get around this error without rebuilding?

Please take note that the patch only addresses CVE-2025-59489 and the issue you are referring to is a completely different and separate matter.

Google requires support for (Link: [INFO] Unity Engine support for 16 KB memory page sizes (Android 15+)) for 16 KB page size and you will need at least Unity 2022.3.56f1+ to have that feature.

Assuming you are not on an Enterprise/Industry license and only Pro licenses, the earliest version that you must be on where you have both the CVE fix and the 16 KB page size support is 2022.3.62f2 and 2022.3.67f2 if you are on Enterprise/Industry.

In other words, no. There is no way to support 16 KB page size on any earlier versions of Unity 2022.3.x that is before 2022.3.56f1. Please upgrade your 2022.3.x projects to the latest version and rebuild the player to rectify this issue.

Thank you for your response.

The problem is that I don’t really want to solve the 16 KB page size issue. I just wanted to patch the build to take care of the CVE-2025-59489 issue. But if I only take care of that, it’s not possible to publish the patched build, because of the 16 KB page size issue.

In this page: Unity Security Vulnerability: Developer Remediation Guide in the Faq section, it says:

QUOTE

My game targets a version(s) of the Android SDK and Google Play does not allow app updates to be submitted to the Play Store. If I resubmit, will my update be accepted?

We have worked with Google to allow a temporary exception to submission rules specifically for the Android SDK for applications that are already live and patched using our provided patching tool. This exception does not apply to other Google SDKs that may have their own version requirements and it may be necessary to update those SDKs before resubmission. Reach out to Google if you need further information or exceptions for your particular application.

UNQUOTE

So, I thought that since the SDK would not need to be updated, and the patch tool succeeded in a new build, I was good to go. But apparently that’s not possible! My build included SDK 33, and is affected by the 16 KB page size issue, which is applicable for Android 15 (API level 35).

Therefore, either the FAQ seems to be wrong, or there’s something that I don’t understand about it, or I’m not using the patching tool correctly. I mean, the game is already live, and unpatched. I patch the offline version using the tool, upload and cannot publish the patched version.

You might be able to request a one time exemption with Google via the Play Console. The language you quoted is right - Google did grant a temporary exemption for resubmitting vulnerable apps. That said it has been a few months so their temporary exemption might have expired. We will clarify it with them.

Thank you for your reply.

The Google deadline was 8 December. So, I did miss it by 16 days, but I didn’t expect they’d be so strict about the SDK version. Actually, the error I’m getting is not about a requirement to submit with the current minimum SDK, which is what I think the exemption was about. Their system seems to accept the patch with the old SDK, but throws an error about the 16KB page size, which is only applicable for newer SDKs.

Anyway, I’ll try to see if I can get an exemption, as you suggested.

Thanks again!