App Store 2.3.13 rejection: In-app events

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps promoting events through App Store Connect.

Apple may be questioning the event card even when the app itself works. Guideline 2.3.13 requires an eligible event, accurate event-specific metadata, correct timing, and a deep link that reaches the event inside the app.

Walk from the card to the event

Check the selected event type, title, images, description, territories, and dates. Does the card describe the event or merely advertise the whole app? We’d test its deep link with both an existing account and a fresh installation.

Align the card and the experience

Correct misleading event details and timing across storefronts. Fix links that land on a generic home screen or an inaccessible feature. If the event charges for digital content, also check the applicable payment rules.

Test the event during the configured availability window using an appropriate test setup. Confirm that users can reach what the card promises and that any paid access is explained.

Give Apple the event identifier, changed fields, and access steps. If the app needs a new build to repair its routing, identify the version containing that fix.

Messages this guide can help with

App Store 2.3.13 rejection; app store 2.3.13 denial; Guideline 2.3.13; In-app events

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review