Developer Reply Not Showing in the App Store? Every Cause, Checked

Nine times out of ten, your developer reply isn't showing because Apple hasn't finished moderating it yet — App Store responses can take up to 24 hours to go live, and nothing is broken on your end. If it's been longer than a day, the usual culprits are a region mismatch (you're viewing a different country's storefront than the review came from), a missing role in App Store Connect, or a review that was edited or pulled after you answered.

Here's every cause, checked in the order worth checking them, so you can tell "just wait it out" apart from "actually go fix something." Work top to bottom and you'll almost always find the reason within a minute or two.

Start here, because it's the answer most of the time. Every developer response on the App Store goes through Apple's moderation before it appears publicly. Apple's own guidance is that it can take up to 24 hours for a response to show up on your product page. In App Store Connect you'll see your reply immediately under the review, but that's just your view. The public listing won't reflect it until moderation clears.

The clock also resets if you edit. Each review holds a single developer response, and editing that response replaces the old one and sends the new text back through moderation. So if you tweaked a reply an hour ago and it vanished from the public page, that's expected — it's re-queued, not deleted.

This one catches teams with a global user base constantly. Reviews on the App Store are tied to the storefront they were written in, and so is your response. A review left in the German store, along with the reply you wrote to it, appears on the German product page, not the US one. If your own device or Apple Account is set to a different region, you can respond in App Store Connect and then never see the reply on your own phone, because you're literally browsing a different store.

To confirm a reply is live, view the listing in the same country the review came from. App Store Connect shows the reviewer's country next to each review; match it, then open that country's storefront (change your region, or check the web listing for that market). The App Store and Google Play differ in a few of these visibility mechanics, and we break the full comparison down in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

You can only respond to reviews that contain written text. A star-only rating (stars with no accompanying words) never appears as a review you can answer in App Store Connect, so there's nothing for a reply to attach to. If someone left you a silent one-star and you're hunting for a way to respond, that's why there isn't one.

It's also worth double-checking you responded to the review you think you did. Long lists, similar complaints, and the same reviewer name across apps make it easy to type a thoughtful reply against the wrong entry. Your reply is live — just under a review three rows down from the one you were staring at.

Responding to reviews is a permissioned action. Per Apple's own documentation, only the Account Holder, Admin, and Customer Support roles can respond to customer reviews. Developer, Finance, Marketing, and the rest don't get the option. So if the "Respond" control is missing entirely, or a teammate swears they replied but nothing ever shows, the first thing to check is the role on that Apple Account.

The Customer Support role exists specifically so you can hand review responses to a support teammate without giving them the keys to your whole account. If that's the setup and replies aren't appearing, confirm with your Account Holder that the role actually saved — an invite that's still pending can look active but can't post.

Reviews aren't frozen. A reviewer can edit or delete their review at any time, and both affect your response. If they delete the review outright, your reply goes with it — a response can't exist on its own without a review to hang under. If they edit the text, only the latest version of the review is ever displayed, and your response stays attached to it.

There's one more path: Apple can remove a review after the fact if it violates the App Store guidelines — spam, offensive content, a competitor's planted rant. When Apple pulls the review, your carefully written reply disappears too, through no fault of yours. If a specific review-and-reply pair you remember is simply gone, moderation on the review itself is the likely explanation.

Once a reply like that clears moderation, it sits publicly under the review for every future visitor to read, which is the entire reason to write good ones. A calm, specific answer to a two-star complaint is quiet social proof for the next hundred people deciding whether to install, and there's real [evidence that replying nudges ratings upward](/blog/does-replying-to-app-reviews-raise-your-rating). If you want the mechanics of who gets notified and where it lands, we cover it in [what happens when a developer replies to your review](/blog/what-happens-when-a-developer-replies-to-your-review).

So a reply that isn't showing is rarely a bug — it's usually moderation still running, a storefront you're not looking at, or a review that changed underneath you. Walk the six checks and you'll know which. And if the real problem is keeping up with every review across both stores before the moment passes, that's the part worth automating. [Start free with ReplyArgus](/signup), no card required, and Argus drafts your first reply in minutes, in the reviewer's own language, with one inbox that tells you exactly what's live.