Update, day 16. Honestly? I'm running out of polite ways to describe this. After SEVEN days sitting in the queue, a reviewer finally opened our resubmission today. Total review time: a few minutes. Result: rejected. "The app launched to an indefinite and unresponsive black screen" on an iPad Air M3, screenshot attached. Except here is what our server logs say: ZERO requests from the review device. Not one packet ever reached us. The same build loads perfectly on our own iPads against production, right now. The reviewer's own screenshot shows a VPN icon in the status bar — our app uses certificate pinning, and any TLS-inspecting VPN kills every request at the client. The device could not reach the internet. The app was reviewed, and rejected, on a connection where no app that talks to a server could possibly work. Yes, part of this is on us and I'll own it: our splash sat there silently instead of saying "no connectivity". That is a real bug and we fixed it THE SAME DAY — visible notice, retry button, resubmitted this afternoon. That is not the part that makes me want to put my head through a wall. The part that does: there is no human being you can talk to. Seven days of silence, then minutes of review on a broken network, then a rejection letter, and now — what, another seven days? One message before rejecting — "hey, black screen on launch, anything on your side?" — costs a reviewer two minutes and would have saved BOTH of us a week. That conversation is simply not available while you sit in the queue. Expedited request: confirmed, then ignored. Support case: "proceeding normally, no action needed", six days later. An App Review appointment: declined. We have a public launch on September 1 and the only thing between us and it is a queue nobody can see into. We did everything you are supposed to do. Fixed every guideline point within hours, attached the demo video they asked for, answered every question in writing. It has not bought us a single day. For anyone else in this thread: if your app pins certificates, assume review happens behind a TLS-inspecting proxy and make absolutely sure your first screen SAYS SOMETHING without connectivity. A silent splash equals 2.1(a), full stop. And log everything server-side — our logs are the only reason we know the device never reached us, instead of chasing a crash that does not exist. Android: same build, submitted today, live within hours. No drama, no mystery, actual release notes. The contrast does itself.

Same boat, only worse. We submitted on 14 August — 15 days ago. We got rejected on the 22nd, fixed all four points the same night, and the resubmission has now been sitting in Waiting for Review for 7 days without anyone opening it. For what it's worth, we tried everything you did and none of it moved the needle: expedited review (confirmed, then nothing), a support case (six days for a reply saying "the review is proceeding normally"), a follow-up on that case (no answer, four days now), and an App Review appointment (declined). We have a global launch on 1 September. At this point we're almost certainly shipping without iOS and postponing it, with everything that implies — marketing, users we've told, the lot. Not great. So I don't have a fix for you, sorry. Just so you know 48 hours is not the ceiling and you probably shouldn't burn your expedite yet if you might need it later. Something broke around the 8 August maintenance and a lot of us have been stuck since.

Your app is indexed and searchable — but only in the US store. I checked with the public iTunes API just now: Searching "YouWorth" in the US store returns your app in position 1. A lookup by ID succeeds for country=us, but returns nothing for country=es or country=gb. So the app is only available in the United States. Anyone searching from another storefront will never see it, no matter what they type. If the people who "cannot find it" are outside the US, that is your answer — check Pricing and Availability in App Store Connect and confirm which countries are selected. Two other things worth knowing: Your original release date is 22 August, but version 1.1 went live on 29 August. Search indexing is not instant — it can take 24-48h after a new version — so if you tested right after that update, you may simply have looked too early. Your listing is English-only. That does not block search, but it limits how you rank on non-English terms in other storefronts if you expand later. You can verify any of this yourself without waiting: https://itunes.apple.com/lookup?id=6762416926&country=us versus the same URL with country=gb. If one returns a result and the other returns zero, it is availability, not indexing.

Update — 29 August. Day 14, still in "Waiting for Review". Answering my own questions in case it helps anyone else here, and adding what we have learned since. TIMELINE 14 Aug — 3.1.1 (170) submitted. First submission after transferring the app to our company account. 17 Aug — Expedited review requested. Got the "We'll expedite review" confirmation. Nothing moved. 18 Aug — Developer Support case opened after 93h waiting. 22 Aug, 19:05 — A reviewer finally opened the app. Eight days after submission. 22 Aug, 19:16 — Rejected on four guidelines: 2.3.6 (age rating), 5.1.1(ii) (purpose strings), 2.1 (questions about our contest), 1.2 (UGC safeguards). 22 Aug, 23:25 — All four addressed. New build uploaded the same night, with the screen recording they asked for attached to the review notes. 24 Aug, 17:29 — Support replied, six days after the case was opened: "the review is proceeding normally, there is no further action you need to take." 25 Aug — Requested a one-on-one App Review appointment. Declined. 26 Aug — Replied to the support case with the current status and our launch date. No answer, three days later. 29 Aug — Resubmission still in "Waiting for Review": 160 hours. 14 days since the original submission. ANSWERING MY OWN THREE QUESTIONS Was it the transfer? Apparently not. The rejection, when it finally came, had nothing to do with the transfer or with ITMS-90076 — it was ordinary guideline feedback. The transfer does not seem to have put us in a slower lane. Did the expedite help? No. Same as Owmince above: requested, confirmed, nothing changed. Same for the support case and for the appointment request. What eventually moved it? Nothing has, yet. FIVE THINGS WE LEARNED THAT MIGHT SAVE SOMEONE TIME The resubmission clock resets, and the UI and the API disagree. When you attach a new build after a rejection, submittedDate in the App Store Connect API resets to that moment. Our App Store Connect page said "submitted 23 days ago" while the API said 2. A rejection response does not appear to be fast-tracked. We assumed answering a rejection would go into a quicker lane than a new submission. Six and a half days in, that is clearly not happening. Support cannot move the queue, and says so. Our case got a polite "proceeding normally" after six days, and the follow-up has had no reply at all. The case number is useful for the record, not for acceleration. Phone support does not cover App Review. The contact options for "App Review Status" offer email only. Apple's telephone support page lists enrollment, membership, app submission and management — App Review is not on it. You can see the reviewer from your own backend. Ours came from 17.234.96.115 — Apple owns the whole 17.0.0.0/8 block — geolocating to San Jose, and the session lasted a few minutes. If you log sessions server-side that tells you far more than the App Store Connect status does. It is also how I know nobody has opened our app since 22 August. We reach our 1 September launch without the iOS build approved and with no way to test the released version with real users first. The version currently live is several releases behind and is missing security fixes that have been sitting in this queue for two weeks. Same genuine question as before: has anyone stuck since the 8 August maintenance actually been approved yet? If so, how long did it take, and did anything unblock it — or did it just eventually happen on its own?