Your app was rejected by App Store or Google Play.

The 5 most frequent causes are: (1) privacy and permissions — App Tracking Transparency incorrectly implemented or permissions without clear contextual justification; (2) payments — use of external payment systems without complying with Apple policies or flows that bypass in-app purchases; (3) content — material violating community guidelines; (4) incomplete functionality — the app crashes or has non-working features during review; (5) metadata — screenshots or description misleading about actual functionality.

It depends on the reason. Metadata problems resolve in 1–3 days. Technical implementation issues (privacy, payments, permissions) require 1–2 weeks of development plus Apple's re-review time — normally 24–48 hours, though it can reach 1 week during high-demand periods.

Yes. Apple and Google Play review every update and can reject features that don't comply with current policies, even if the previous version was approved. Policies evolve — especially around privacy, payments and AI-generated content — and what was valid 18 months ago may not be today. A technical audit before each major update prevents surprises.

This is common. Apple's rejection messages are often generic and don't specify exactly which code or flow violates the policy. The correct process is: (1) review the message looking for specific guideline references; (2) audit the described functionality; (3) prepare a reviewer response with the change made and its justification. Apple allows responses before resubmission when there's ambiguity. Dribba manages this process end to end.