After using the Quest 3S referral code, only the referring account does not receive Meta credits.
【Environment】 ・Device: Meta Quest 3S ・Referral Type: Headset Referral Program ・Region/Store: Japan 【Situation】 ・I own two Meta accounts. - Account A: The account I normally use on Meta Quest 3 - Account B: An account with no headset usage history ・After logging into the web version with each account to check, the “Referrals” tab was only visible on Account A. ・Therefore, I determined Account A was the account capable of issuing referral links and sent my family a Quest 3S referral link from Account A. ・My family member clicked that referral link, created their own Meta account, and completed the Quest 3S setup. ・After setup completion, Meta Credits were correctly awarded to the family member's account. ・However, Meta Credits were not awarded to my Account A, the referring account. [Confirmed Details] ・Confirmed the family member used my referral link. ・Re-logged into both the Meta Quest app and browser on Account A and checked the Wallet/Credit balance, but no referral credits were displayed. ・Should not have forgotten to use the referral code or sent it from another account. 【What I Want to Know / Consultation】 ・In this situation where “only the referred party received credits, not the referrer,” are there any possible causes? ・If there is a delay in reflecting referral credits, what is the maximum waiting period? ・If this is a system issue or requires manual intervention, please advise which support channel to contact and what information I should provide.
Worlds horizon is « unavailable » but I live in France ! Heeeelp
I bought my brand new meta quest 3 and I suddenly don’t find worlds available for the download. I used my meta profil in another meta quest 3 headset a couple of weeks ago but I wasn’t the owner of that headset, but worlds worked just fine. I haven’t been banned or anything. I just can’t download it on my meta quest as if it wasn’t supported but I live in France and it’s on the supported counties list ! What can I do ??
Can not pass VRC.Quest.Functional.6 (App must only include Quest HMDs and controllers...)
Hello All, I submitted app on app lab. After released app, get response from oculus that Changes requested and can not pass VRC.Quest.Functional.6 (App must only include Quest HMDs and controllers...) Anyone have an idea how can pass this VRC.Quest.Functional.6 requirements?
can't pair Quest 3 with meta app on phone
My iPhone app says it found the headset, but the headset does not display the 5 digit code needed to complete the pairing. Instead my Quest 3 only offers the accounts that already are already set up in it. I have updated both the Quest 3 software and my iPhone Meta app, and restarted the headset twice to no effect.Ongoing App Discoverability Issues Post-Recent Meta Horizon Store (Merging of App Lab & Main Store)
Hello fellow developers, I wanted to bring attention to an important issue that I’ve encountered since the merging of the stores, which I believe might be affecting more than just my app. After releasing an update to my app with the new metadata, I noticed a sharp decline in searchability—users can now only find my app by searching the exact name, whereas previously relevant keywords worked well in the search. I've been in communication with Meta's Developer Support team, who have acknowledged the issue and are working on it internally. However, I felt it was important to raise this in the community because this may be affecting other developers, particularly those who rely on searchability for discoverability and revenue. Here’s the situation: Only exact-name searches return my app in search results, despite all keywords being properly entered and compliant with guidelines. This issue arose immediately following the 5th August launch of the Meta Horizon Store. Meta is aware of the problem but has not provided a concrete timeline for resolution or clear interim solutions. If any of you are experiencing similar challenges, I think it’s crucial that we start a discussion. Discoverability is vital for every developer on the platform, and if this is a broader issue, we may need a more transparent approach from Meta, such as flagging it as a known issue. In the meantime, if you’ve encountered this issue and found any effective workarounds (such as changes to app metadata, or modifications to Early Access settings), I’d be grateful to hear your thoughts. Thanks for reading, and I look forward to hearing your thoughts and experiences.Enhanced Panorama Viewing with Passthrough and Wall-Locking
Current Situation Currently, panoramas on Meta Quest are displayed against a plain background, which doesn't take advantage of the device's mixed reality capabilities. Proposed Improvement I suggest implementing a new viewing mode for panoramas that combines passthrough technology with the wall-locking feature seen in YouTube VR's mixed reality environment option. Key Features Passthrough Integration* Allow users to view panoramas with the real-world environment visible in the background using the Quest's passthrough technology. Wall-Locking Option Implement a feature similar to YouTube VR's mixed reality mode, where users can "lock" the panorama display to walls or surfaces in their physical space. Flexible Viewing Give users the option to switch between the current plain background mode and this new mixed reality mode. Adjustable Opacity: Allow users to adjust the opacity of the passthrough background to find their ideal balance between the panorama and their real environment. Benefits Enhanced immersion by blending virtual panoramas with the real world More natural and comfortable viewing experience, especially for longer sessions Increased spatial awareness while enjoying panoramic content Versatility in how users can experience their panoramic photos and videos
