What causes a store not loading products?

The product list is not fetched from the store, the product IDs do not match the store configuration, or the fetch fails without handling, so the shop appears empty.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Store or Shop Not Loading Products

Quick answer: Fetch product details from the store with matching IDs, handle fetch failures with retries, and confirm the products are approved and available.

A store not loading products is a fetch or config problem. Here is how to fix it.

How to fix it

1. Fetch with matching IDs

Fetch the product details from the store using product IDs that exactly match those configured in the store console. A mismatched or missing ID returns no product, so the shop shows nothing.

2. Handle fetch failures

Network failures and store-not-ready states make the fetch fail. Handle these with retries and a loading or error state, rather than showing an empty shop, which looks broken and loses sales.

3. Confirm products are available

Products must be approved, priced, and available in the player's region to be returned. A product in draft, unpriced, or not available in the region does not appear. Confirm each is fully set up and live.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every mobile error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.