App Store 4.2.1 rejection: ARKit experiences

Apple cited 4.2.1 because the augmented reality feature may do too little. This rule is specifically about ARKit experiences, rather than the whole of minimum functionality under 4.2. Simply placing a model in an AR view or replaying an animation doesn’t meet Apple’s stated expectation.

Check what the person can actually do

Open the feature on a supported device and describe the task it helps someone complete. Does the AR interaction contribute to that task, or is it a standalone visual effect? We’d test with someone who hasn’t seen your demo explanation; the useful interaction needs to be discoverable in the app.

For illustration, a placement tool could let someone meaningfully inspect or interact with an object in their space. That’s a product-design example, not a feature checklist that guarantees approval.

Improve the experience and show it

Build the interaction into the app’s real purpose. Adding an unrelated AR button elsewhere won’t explain the value of the rejected feature. Include clear instructions, handle unsupported conditions, and test the full task on hardware rather than relying only on a simulator.

Give Apple the route to the feature, what the user can accomplish, and a short recording if it clarifies the interaction. Distinguish a feature the reviewer couldn’t discover from one that genuinely needs more development.