Skip to main content
New Participant
March 30, 2026
Question

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!

2 replies

Degly
Inspiring
April 1, 2026

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.

cheesepantz
Inspiring
May 1, 2026

We are still getting these errors on our live build. It is hard to grant consumables and durables items when the api call fails due to 2002 errors. Currently happening on Sail at random times it just throws the error.