Skip to content
Keshav Raj
A phone's memory pages aligned neatly and a store gate lifting its barrier for the apps.
SECURITY QUARTERFLEET UNBLOCKED
SHIPPED 16 KB page size and TrustManager fixes cleared store blocks fleet-wide.I OWNED ImplementerOUTCOME FLEET UNBLOCKED

Play policy compliance

Keshav RajImplementer · 2025–26 · ShippedContact meResume PDF

Context

Google Play and the App Store can block updates when an app breaks a policy. Because the ed-tech company ships about 660 white-label apps from one codebase, one issue blocks the whole fleet. I implemented the fixes in 2025 and 2026.

The problem

Two Play policy issues stopped releases fleet-wide. One was page size: the native libraries were not aligned for 16 KB pages, which Play requires. The other was an unsafe TrustManager warning, with a deadline of 1 January 2027.

What I did

  1. For page size, I restored 16 KB alignment in the native DRM SDK, in release 3.1.133.

  2. I raised the versionCode base fleet-wide, from 60000 to 70000.

  3. For the TrustManager warning, I changed the local playback proxy in the WebView so that it trusts only the proxy certificate, through the platform TrustManagerFactory, instead of trusting everything.

  4. I also cleared an App Store rejection for private APIs, in a separate release.

Key decision

I pinned trust to one certificate instead of adding a blanket exception. It was more work, and it also removed a real weakness.

The cost was careful testing of local playback on many devices.

Result

The 16 KB rejection was cleared fleet-wide, and the TrustManager fix landed for every white-label app ahead of the 1 January 2027 deadline.

What I learned

Because one codebase feeds every school, one fix is cheap and one mistake is expensive. I would keep a pre-submission compliance checklist.

Stack

  • Android NDK
  • C
  • Kotlin
  • Gradle
  • WebView
Play the world →