App update stuck in “Ready for Distribution” for 3 days, still showing old version

App Store Distribution & Marketing General
bclouser OP
Created
Replies 2
Boosts 0
Views 90
Participants 2

My update for Mktbox: Stock & Portfolio App (Apple ID: 1237897006, version 27.0) was approved and has been in “Ready for Distribution” since [October 11], with automatic release enabled. The App Store still shows the previous version on all devices I’ve checked.

What I’ve verified:

Release is set to automatic, with no scheduled date Agreements, Tax, and Banking are all active Pricing and Availability is unchanged

I opened support case 102994667282 a few days ago and followed up, but haven’t had a reply. The contact form only offers email for this topic.

Could someone from the App Store Connect team look into the release status? Any pointers from others who’ve hit this recently are also appreciated.

Replies  2
Boosts 0
Views  90
Participants  2
lkolebka OP

Hi there! I'm in the same boat as you for two of my apps not showing the update after they have been approved for both iOS and MacOS.

That's really frustrating. I was on the phone with an Apple Advisor from the Developer Support team and they confirmed everything is alright with my account (every agreement is correctly signed etc).

Not sure what to do. I even hesitated pushing another update with manual release with hopes this will unlock the situation.

Curious to see how the situation is evolving for you.
lkolebka OP

Update: Both of my apps are now showing the approved versions on the App Store. Brim 1.4.2 is live. Screeny was fixed even before I pushed its new update, so it looks like it resolved on its own (after 6 days).

I still don’t know what caused it. I submitted a new build (Brim 1.4.2) and escalated through Developer Support, but since Screeny cleared without any new submission, I can’t say the new build is what unblocked things. If you’re stuck in the same way, it may be worth opening a case with Developer Support and mentioning the app’s Apple ID and the approval date, but a new update doesn’t seem to be required.