Forum Discussion

user_462919330115905's avatar
18 days ago

Error 2002: Failed to fetch IAP purchases – get_viewer_purchases failing since Mar 27

Hi all,

 

We've been experiencing a sudden and persistent Error 2002 ("Failed to fetch IAP purchases") since March 27, 2026. The error occurs when calling iap.get_viewer_purchases via the Oculus Platform SDK, and it's affecting subscription status checks at app launch.

 

Environment:

  • Meta XR Platform SDK: 77.0.0
  • - Unity: 6000.0.68
  • - Affected devices: Meta Quest 3S, Quest 3, Quest 2 (confirmed on all tested devices)
  • - OS: Android 14

Impact:

Approximately 1/3 to 1/2 of our daily active users are encountering this error. The issue began on March 27 with no app update or any change to our IAP configuration in the Developer Dashboard on our side.

 

Issue summary:

Since March 27, calls to get_viewer_purchases consistently return error code 2002. The error originates in PurchaseFetcherImpl.getAppGroupingId() and propagates up through the IAP service layer:

 

Error AppManagerClient at horizon.platform.service.iap.PurchaseFetcherImpl.getAppGroupingId(:23)
Error AppManagerClient at horizon.platform.service.iap.PurchaseFetcherImpl.getViewerPurchases(:2)
Error BasePlatformServiceProvider QPL Event Fail: {"error":{"code":2002,"message":"Failed to fetch IAP purchases"}}
Error Unity GetViewerPurchases error: {"error":{"code":2002,"message":"Failed to fetch IAP purchases"}} (Error Code: 2002)

The failure at getAppGroupingId level suggests the app's IAP grouping configuration may not be resolving correctly on the platform side. Given that the error started suddenly on March 27 without any changes on our end, we suspect this may be related to a platform update or a backend configuration change.

 

Could anyone from Meta or the community help clarify what might have changed on March 27, or suggest any steps to investigate further?

 

Thank you!

1 Reply

  • Degly's avatar
    Degly
    Start Partner

    That’s typically a backend regression or rollout (especially with the getAppGroupingId() failure).

    But realistically, this needs Meta to fix on their side. I’d escalate via Developer Support ticket + include logs + timestamp (since Mar 27) this kind of issue usually gets patched silently once reported.

→ Find helpful resources to begin your development journey in Getting Started

→ Get the latest information about HorizonOS development in News & Announcements.

→ Access Start program mentor videos and share knowledge, tutorials, and videos in Community Resources.

→ Get support or provide help in Questions & Discussions.

→ Show off your work in What I’m Building to get feedback and find playtesters.

→ Looking for documentation?  Developer Docs

→ Looking for account support?  Support Center

→ Looking for the previous forum?  Forum Archive

→ Looking to join the Start program? Apply here.

 

Recent Discussions