New Resource Guide Available: Simplifying Payouts for Developers!
Hello Developer Community, We’re thrilled to share our brand new resource guide: Payouts Made Simple for Developers! With 14% of Non-Technical Support Tickets being payments related, we wanted to find better ways to help solve common issues, so you can focus on building great apps and getting paid quickly for them. What’s It About? Whether you’re new to the platform or have managed payouts before, this guide is here to make payouts easy, clear, and hassle-free. It walks you step-by-step through everything you need to know—from setting up your account to receiving payments with minimal stress. Key Benefits Clear instructions for account setup, bank verification, and tax requirements Easy troubleshooting for common issues and payment delays Handy tips to help make sure your payouts are processed quickly Access to support resources right when you need them Get Involved! We want this guide to be as helpful as possible. Please check it out, try the suggestions, and let us know what you think! Your feedback helps us improve. If you spot something confusing or think we missed an important topic, drop a comment below! Already a payouts pro? Share your experience and best tips in the thread! Check out the guide here, and help us make Developer payouts smoother and simpler for everyone!
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
technical issues
hello i am a game creator and i need help i have the when i try to load into my game it just doesnt let me get in its stuck at the loading part i didint add any loading screens just straight into the game and it just doesnt get in please help this is just killing my motivation i had this in all of my projects
Meta Developer Admin Verification
So I'm trying to launch my game onto applab and my game has been accepted but i need to verify my organization to actually release it. I tried doing the admin verification but it comes up as verification under review and it wont let me provide documents or anything for said verification. I waited a couple of week and i checked again. Still no acceptance and it still said verification under review . Any way to help or fix this?
How to use a new keystore for Quest 3 builds. I can't find how to delete existing builds.
Hi everyone, I'm trying to upload new builds for my Quest 3 app using a different keystore, but I've hit a wall and hoping someone here can help. The official documentation at https://developers.meta.com/horizon/resources/publish-overview-appID/ states: The only way to generate a new keystore is for you to delete every version of your build However, I cannot find any option to delete builds anywhere in the Meta Horizon dashboard. I've looked through the app management pages, version history, and release channels, but there's no visible delete button or option. Thanks!pages_read_engagement permission present in token scopes but API returns error
We are experiencing an issue where the pages_read_engagement permission is correctly granted (Advanced Access) and confirmed present in our Page Access Token scopes, yet all engagement-related endpoints return error #10. App info: App Mode: Live Graph API version tested: v24.0 and v21.0 (same result) Token verification via /debug_token: { "data": { "app_id": "....", "type": "PAGE", "is_valid": true, "scopes": [ "pages_show_list", "business_management", "instagram_basic", "instagram_manage_insights", "instagram_content_publish", "pages_read_engagement", "pages_manage_posts", "public_profile" ] } } As shown above, pages_read_engagement is explicitly listed in the token scopes. Calls that FAIL (error #10): GET /{page_id}/posts?fields=id,likes.summary(true) GET /{post_id}/likes?summary=true GET /{post_id}/comments?summary=true Error response: { "error": { "message": "(#10) This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature.", "type": "OAuthException", "code": 10 } } Calls that SUCCEED with the same token: GET /{page_id}/posts?fields=id,message,created_time → ✅ OK GET /{page_id}?fields=followers_count,fan_count → ✅ OK GET /{page_id}/posts?fields=id,shares → ✅ OK Steps to reproduce: Create a Page Access Token via Facebook Login for Business with config_id that includes pages_read_engagement Verify pages_read_engagement is in token scopes via /debug_token Call GET /{page_id}/posts?fields=id,likes.summary(true) with this token Observe error #10 despite the permission being present Expected behavior: The call should succeed since pages_read_engagement is in the token scopes and granted in Advanced Access. Actual behavior: Error #10 stating the endpoint requires pages_read_engagement — the very permission that is already granted. Additional context: The token is obtained via Facebook Login for Business (using config_id, not explicit scopes) Instagram endpoints using the same token work correctly (instagram_manage_insights which depends on pages_read_engagement) We have requested pages_read_user_content twice and it was rejected both times The issue is reproducible across API versions (v21.0 and v24.0)🚀 Store-Ready VR: The Launch Checklist
There's a big difference between "the build works" and "this is ready for customers." Nailing that last stretch right is what separates a smooth launch from a stressful one. In this session, Meta Horizon Start Mentor Shane Nilsson breaks down the non-obvious work that goes into making a VR project truly launch-ready—from store page setup and trailer prep to ratings, compliance, QA readiness, and patch planning. The goal: help teams avoid common launch-week mistakes and ship with confidence. What to expect: Store page fundamentals—what your page needs to look like before you go live Trailers, screenshots, and positioning—how to present your project so it lands with customers Ratings and compliance—the stuff that's easy to overlook until it's a blocker QA and patch planning—how to make sure you're actually ready, not just "done" Common launch-week mistakes and how to avoid them before they happen Join on Zoom
Can anyone help me?
Im a 12 year old who has just made a VR game with unity and want to upload to applab, my APK is working and there is no errors uploading and the release channel is ALPHA, but i need to verify my organization with either legal documents or a government issued ID, can anyone help me upload?ERROR_CLOUD_MESH_UPLOAD_FAILED(-400039)
Unity colocation build with MRUK, getting this error in Logcat and "host can't share the room with group xx-xx.." on immersive debugger... User ID and User profile active in dashboard, device has spatial permission enabled, project uploaded to alpha channel, my own user invited as tester, Keystore signed, tried with 4 different WIFI, no LLM has a clue... was working before upload alpha, What else should I check?[New navigator update] No app icon and name
Hi! My Quest 3 recently updated itself to newer OS with reworked navigator. The issue is, that the exact same app (literally the same .apk file) now shows default icon and no name in the taskbar. Previously there was a logo and correct name. FYI this is fully proprietary, in-house only app. It isn't on marketplace nor it ever will be as it's our internal tool. It's just bad UX for us so I want to fix that. Also it never shows on the installed apps list, only in hidden "Untrusted sources" - can I overcome that without using marketplace? I use UE5, and those are values i set (that worked perfectly fine before but after the update they don't) DefaultEngine.ini PackageName ApplicationDisplayName VersionDisplayName DefaultGame.ini ProjectID ProjectName Description CompanyName I would like to kindly ask for you support on this matter. Best regards!
