Your app is approved. So why can't anyone find it?

The approval email is real, the status says released, and yet typing your app's exact name into the store returns everything except your app. Almost every first launch hits this moment, and almost nothing about it is broken. Between "approved" and "findable" sit four separate systems with four separate delays — and none of them reports where you are in the queue.

Approved isn't released

Approval means one thing: the binary and listing passed review. Whether anything ships next depends on a setting you chose at submission, possibly weeks ago. Apple gives you three release options — release automatically on approval, release manually, or release automatically no earlier than a date you picked. If you chose manual, the version now sits at Pending Developer Release until you press the button; the store is waiting on you, not the other way around. Google Play's equivalent is managed publishing: when it's on, approved changes queue up in the publishing overview until you explicitly send them live.

The single most common launch-day "bug" is a manual release selected months earlier and forgotten. Before you debug anything downstream, read the status line. It should say Ready for Distribution on Apple, and Play's publishing overview should be empty.

Released isn't propagated

Pressing release doesn't flip one switch — it starts a rollout across a distributed catalog with regional storefronts and layers of caching. Apple's own guidance is that a released app can take up to 24 hours to appear on the App Store; in practice the direct product page usually resolves within an hour or two, with full propagation across every storefront trailing behind. Google Play publishes on a similar "processed, not instant" basis — and for a first app from a new developer account, the review before that can already run up to seven days, sometimes longer, by Google's own numbers. (More on the review clock itself in How Long Does App Review Actually Take?)

The useful consequence: there is a stretch of hours where your direct link works and nothing else does. If the link loads a product page, the launch is fine — you're just early.

Propagated isn't indexed

This is the stage that actually generates the panicked forum threads. The search index is a separate system fed by the catalog, and neither store publishes a service-level agreement for it. A brand-new app — zero downloads, zero ratings, zero search history — commonly takes anywhere from a few hours to a day or two after the listing is live before an exact-name search returns it. Every launch thread on the developer forums has the same arc: alarmed post, someone says wait, it appears.

Separate that delay from a different problem that looks identical: ranking. If your app is called something generic — Budget Tracker, Habit Coach — you can be fully indexed on day one and still sit behind forty incumbents with years of install history. That doesn't fix itself by waiting. The quick test is to search the most distinctive token in your name: if the made-up brand word doesn't return you, you're still indexing; if it does but the generic phrase doesn't, you have a ranking fight on your hands — which is really a naming decision you take from here.

Plan launch day around the pipeline

Once you know the stages, the launch-day playbook writes itself. Decouple your announcement from the approval email: choose manual release, and press it when you're awake, watching, and ready — not whenever review happens to finish. Lead every announcement with the direct link, which you can construct before the app is even out: Apple product pages live at apps.apple.com/app/id<your Apple ID>, and Play URLs are just play.google.com/store/apps/details?id=<your package name>. "Search for it in the App Store" is the worst possible call to action in your first 48 hours; the link works a day before search does.

And when you verify, don't trust the phone in your hand. Your own store app has cached state, your account has a region, and availability differs by country. Check from a second device, a browser in a private window, or a storefront you don't normally use.

When to actually worry

Give the index 48 hours from the moment the direct link works. If the exact name still returns nothing after that, run down this list before writing to support:

Availability. Is the country you're searching from actually in the app's availability list? A direct link that 404s in one region but resolves in another is an availability setting, not an indexing failure.

The right track. On Play, confirm it's the production track that went live. An approval email for a closed-testing release looks a lot like the real thing, and a closed track is invisible to the public by design.

The right status. Back to stage one: Pending Developer Release means the store never got the go signal. It happens embarrassingly often, which is why it's both the first and the last check.

If all three pass, the link works, and search still comes up empty, then you've earned the support ticket — genuinely stuck listings exist, but they're the rare case. The boring truth is that the pipeline almost always finishes on its own; the panic window is just wider than anyone expects the first time.

Search lag ends. The listing is forever.

The index always catches up — and from that point on, what decides installs is what people see when they land: the screenshots, the subtitle, the first two frames in search results. That part you control completely, and it can be ready before the approval email ever arrives. ShotCanvas turns raw screens into a store-ready set for every required size on both stores, so the listing is the one launch-day system with zero lag.