XmasMaps (Team ID: 34WAQXFJHP) Stuck in "Waiting for Review"

Question

Created 1w

Replies 1

Boosts 0

Participants 2

To Apple Engineers,

I don't seem to get any updates or responses so I will keep trying to reach out here. Please work with me on what is needed to get my app approved.

it is truly important to get it deployed as soon as we can so I can begin to launch and promote the app in App Store.

It has already been live on the Google Play Store for a couple weeks.

My app: XmasMaps has been going from "Waiting for Review" to "Rejected". I would fix the mistakes right away which would put XmasMaps back into "Waiting for Review".

This App would be a useless App after November.

Our app, XmasMaps, has been stuck in "Waiting for Review" since September 29th, 2026 (Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc).

Timeline of previous actions:

Sept 29, 2026: Initial submission

Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections

Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review"

Oct 16, 2026: Expedited review request submitted

Oct 19, 2026: Support customer inquiry submitted

Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season.

Oct 24, 2026: Rejected again for something already built into my latest build. i resubmitted right away and now put back into "waiting for review" when I would expect that the engineer who rejected it would take it back and finalize my app.

Oct 28, 2026: As of today, I opened multiple app requests for an update and update the forum multiple times until I can try to get a response.

Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc
Support Case ID: 102982950152 / 103008467960
Team ID: 34WAQXFJHP

I ask, please assist and review my app. I really need it live on both platforms to promote it.

Please let me know if any additional information is needed from my side.

Thank you.

Answer 1 · 1d

GetResubmit OP

1d

Since the October 24 rejection reportedly concerns something already present in the submitted build, I’d make the next reply easy to verify against that exact build.

Put together a short timeline listing each submission date, version and build number, the guideline cited, the requested change, and where that change appears in the next build. For the latest build, include:

A screen recording starting from a fresh install and showing the relevant feature end to end.
Numbered steps that reproduce the flow, including any account, location, date or permission settings needed.
The exact device and OS used, plus confirmation that the App Review account can reach the same screen without special setup.
A concise comparison showing what changed between the rejected build and the current submission.

In App Store Connect, ask the reviewer to identify the build number and the specific step or screen where the expected behavior was missing. Avoid relying only on “this is already fixed”; connect the fix to a visible screen and reproducible steps.

You could write:

“The October 24 rejection refers to [issue]. This behavior is present in version [version], build [build], submitted on [date]. The attached recording shows it from a fresh install; steps to reproduce are: [steps]. The relevant change from the previously reviewed build is [specific change]. Could you confirm whether the review was performed on build [build] and identify the step where the expected behavior could not be verified? We have kept the review account and test environment available.”

Since the app’s value is seasonal, keep the response focused on the verification details that could resolve the current rejection quickly.