Troubleshooting offers that disappear on login or reappear after refresh

If an offer is visible for some players only after refreshing the Hub Store, or behaves differently before and after login, check the item's visibility rules first. This pattern is often caused by item configuration rather than a storefront rendering issue.

What to check

1. Purchase limits
   Review the item's purchase restriction settings, such as Max purchases per user, reset behavior, and whether the item is hidden after the limit is reached.
2. Segmentation rules
   Review any player-attribute-based visibility rules, for example conditions such as Player.is_vip == false with the item hidden otherwise.
3. Player attribute updates
   Confirm that the game updates the relevant player attribute on Aghanim after a successful purchase. If the attribute is not updated, the offer may continue to appear or disappear unexpectedly depending on the active visibility rule.
4. Existing purchase history
   Check whether affected players already have successful purchases for the SKU. If they do, a lifetime purchase limit may be hiding the item as configured.

Why this happens

Offer visibility can differ between anonymous and authenticated states because authenticated sessions have player data available for segmentation evaluation. If an item combines a purchase limit with segmentation rules, outdated or conflicting configuration can make the offer appear inconsistent on login.

Example resolution

In one resolved case, a VIP offer was missing for some mobile users on login because the item still had an old max purchases per user: 1, no reset, hide from store when reached limitation. That limitation was no longer aligned with the intended setup after a newer is_vip attribute-based approach was introduced. Removing the obsolete purchase limitation resolved the issue.

Recommended fix

• Use one clear source of truth for offer eligibility whenever possible.
• If eligibility is controlled by a player attribute, make sure that attribute is updated reliably after purchase.
• Remove legacy purchase limits if they are no longer part of the intended logic.
• Retest with affected player accounts after updating the item configuration.