False Rejections — Long Review Times — Insufficient Directions

Our game Sand Sort 3D was rejected under Guideline 4.3(a) for binary similarity with our other titles. Three problems:

False rejection: it's an original game: its simulation code, shaders and levels exist in no other app. The flagged overlap is shared infrastructure, not content: Unity engine resources, brand fonts, licensed Asset Store packs, and our own internal SDK (sign-in, IAP, ads, cloud save, analytics, consent) that we reuse across our catalogue. On our own audit, engine and font data are the bulk of the overlap; content we designed is ~4%, limited to a coin icon and a settings toggle. No gameplay code, levels, art or design is shared with anything we publish.

Insufficient directions: the notice cited 4.3(a) without naming a single element of the app, so we have no actionable way to comply. If it's rejected again, please identify the specific content at issue.

Long review times: this rejection has held the release 15 days, and review on this app and our other titles is averaging 10+ days — unusually long. A component-by-component breakdown is attached as appeal; the game is already live on Google Play.

False Rejections — Long Review Times — Insufficient Directions
 
 
Q