Google Play Android Emoji Policy policy: fixes and checks

Apps running on Android 12 or later need to support the latest Unicode emoji. Custom emoji implementations must add support within four months of a new Unicode Emoji release.

What to check

Identify whether text uses the default Android emoji implementation or a custom font, keyboard, renderer, or third-party library. Default Android emoji already meets the policy’s stated support path on Android 12 and later.

Test newly released emoji in messages, names, search results, and other text surfaces. A missing-glyph box in one custom component can reveal a stale implementation even when another screen renders correctly.

How to address the rejection

Update the custom library or use Android’s supported modern emoji handling. Verify compound sequences and user-generated text as well as a simple emoji picker.

Check the current Unicode release and the official Android implementation guide when preparing the fix. In review notes, identify the updated dependency and the affected text surfaces, rather than assuming the device’s system font updates every custom renderer automatically.