Why it appears
Even Kotlin/Java apps can bundle native code through analytics, media, games, security or other SDKs. A single old native library can trigger compatibility warnings.
Inspect the release artifact
Identify all ABIs and .so files in the AAB/APK. Map each native library back to your codebase or vendor dependency.
Update the source of the problem
Where the library is yours, update the NDK/build configuration. Where it is vendor-provided, move to a compatible SDK version or request an updated binary.
Rebuild and verify
Generate a fresh release artifact and check the packaged native binaries rather than assuming a source change solved the problem.
Avoid blind upgrades
Large dependency jumps can cause new runtime or API issues. Keep a record of each changed native dependency and retest affected features.
Official sources
Policies and platform requirements can change. Check the linked official documentation for the latest wording before acting on a time-sensitive case.
Need case-specific help?
If your situation includes a specific warning, rejection or account state, send the exact notice rather than applying generic steps blindly.
Request assessment