Business Verification 'In Review' 10+ days — blocking App Review submission
Hi everyone, I'm building ZynPost (zynpost.co.uk) — an AI-powered social media scheduling platform for small businesses. I submitted my business verification over 10 days ago and it's still showing "In Review" with no updates. Details: Business Portfolio ID: 1514153376737761 Use case selected: "App requires access to permissions on Meta for Developers" App name: ZynPost App status: Published (Live mode) The problem: The pending business verification is blocking me from completing my App Review submission. Specifically, instagram_business_content_publish requires Advanced Access which requires Business Verification to be complete before I can run the required API test call. This means I cannot submit my App Review until verification completes. I have completed everything else: All permission descriptions written All screen recordings uploaded Facebook OAuth working and tested Instagram connected and tested All other API test calls completed I've tried raising a support ticket through the bug reporter but was told individual cases can't be handled there. Is there any way to escalate this or get a manual review? Any help from Meta staff or community members who've resolved this would be greatly appreciated. Thank you
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!
Accessibility Feature Request: Conversation Focus Mode for Ray-Ban Meta Display Glasses
Hi everyone! I’m a Ray-Ban Meta display glasses user who is hard of hearing and wears hearing aids daily. I’d love to see a conversation focus mode added that prioritizes voices directly in front of the wearer and reduces background noise. In busy environments, this would make a big difference for hearing-aid users and others who rely on clearer speech in real time. If this type of accessibility feature is ever developed, I would absolutely love the ability to have it added to my glasses and would be happy to provide feedback or participate in any beta or user-testing opportunities. I’ve also submitted this through support channels, but wanted to share here in case the team is gathering feedback.IAP not working and freezing headset.
We have an app on the Meta Store where IAP has been working perfectly fine. Over the past month we have noticed a spike in mobile purchases and zero In app purchases. Upon investigation it appears that in headset when you try and make a purchase, it allows you to select the item for purchase, see the details of said item, check the consumer agreement box and put in your pin. But as soon as you hit purchase, it hangs for a few seconds then displays "oops, something went wrong, try again later", then locks the headset so the only option you have is to reset the headset. (Though some of us never got that far and it locked the headset out immediately on selecting the item) With the last update we pushed and for a few months, everything was working perfectly fine with the IAP system. Now, with no update or build from our side, it is not working. Any help would be greatly appreciated. Cheers
Performance drops when using Passthrough Camera Access API in Unity
I’m working on a small AR project for a personal website modernfoodcatering.com and integrating the Passthrough Camera Access API in Unity. I’ve noticed significant frame drops and lag when multiple objects are rendered in the scene simultaneously, even with basic meshes. Has anyone encountered similar performance issues in Unity with the Passthrough API, and are there best practices to optimize rendering for smoother interactions? Any advice would be greatly appreciated.
A refund REST API error has occurred.
All other Server APIs have been confirmed to be functioning properly. When checking the SKU via viewer_purchases, refund_iap_entitlement returns the "error_user_msg": "We can't find your order at this time." We are still in the development stage before the launch. Thank you. HTTP/1.1 400 Bad Request { "error": { "message": "An unknown error occurred", "type": "OAuthException", "code": 1, "error_subcode": 1891060, "is_transient": false, "error_user_title": "\uc8fc\ubb38\uc744 \ucc3e\uc744 \uc218 \uc5c6\uc2b5\ub2c8\ub2e4", "error_user_msg": "\ud604\uc7ac \ud68c\uc6d0\ub2d8\uc758 \uc8fc\ubb38\uc744 \ucc3e\uc744 \uc218 \uc5c6\uc2b5\ub2c8\ub2e4.", "fbtrace_id": "APeiCD1VcJp0x3hE5hbRCev" } }
