Oculus Spatial Anchor drifts in the Passthrough space
I’m trying to spawn a Cube as spatial anchor. But after spawning it drifts if I move physically. I’m add OVRSpatialAnchor after instantiating like this, _cube.AddComponent<OVRSpatialAnchor>(); Please correct me if I have to check something on the build settings or some Oculus settings in Unity. Thanks guys!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.
Cannot Add New User to Release Channel (Meta email vs. Oculus email?)
Hello, we are developers of a VR app. When we tried to add a new Meta account email to our app's Release Channel on Oculus Developer (https://developer.oculus.com/), we got this message: "We couldn't find anyone with the Oculus email." This email is a newly-created Gmail that has just signed up for a Meta account on https://auth.meta.com/. This email is not a Facebook account. Did something went wrong, or is there a step missing? I thought by registering a Meta account, this email is already an Oculus account.
Meta Avatar - Failed Entitlement check 7 - user doesn't have app in library
H all, I made a side-loading build of an oculus app with meta avatar feature in Unity. I am able to load and see my avatar, but the other users that are part of my organization can't. They got that message "Failed Entitlement check 7 - user doesn't have app in library". Is there any solution? Thanks in advance.Meta Quest Webhooks for IAP - Documentation about the application order status event
Context: I would like to subscribe to webhook events to receive notifications whenever a user's subscription changes (ex: buying a subscription, canceling a subscription, changing the subscription date, etc.) Possible solution: According to the official documentation, it seems to be possible to subscribe to webhook events to receive real time notification whenever the Application object changes. The Application object seems to have 3 fields, join_intent, create_new_session and order_status. I think that subscribing to the order_status field would send events whenever a user's subscription would change. Problem: I can't find any documentation about the order_status field. There is some documentation about the join_intent field, however the only thing I found about the order_status field is this sample from the Oculus dashboard (when subscribing to the Application webhooks): { "field": "order_status", "value": { "event_time": "1659742639", "user_id": "10149999707612630", "product_info": { "notification_type": "PURCHASED", "reporting_id": "03f8833e-9c02-4fa0-978f-4cfe91f86bae", "sku": "item_sku_1", "developer_payload": "{\"quoteId\": 1234567}" } } } In order to receive events about changes to user's IAP (subscriptions and one time purchases), I would like to get more information about the order_status field webhook event. More precisely, it would be great to know all the possible values that the notification_type field could have (other than "PURCHASED"). Thank you.
Closing thoughts...
--------------------------------------- DISCLAIMER: Things can greatly change during the upcoming days, and this could end up no longer being true in that time, so be sure to take all of this with a grain of salt. --------------------------------------- Tomorrow, in about 7 hours, will be the day Meta will force us Quest users to migrate our accounts to Meta accounts in order to keep using our Quest device. Tomorrow will also be the day I will take my only headset (Quest 1), package it neatly into the box it came in, and shelve it for an unspecified amount of time. I will not go through the process of migrating my Oculus account into a Meta account. After all the privacy snafus that the company formerly known as Facebook has had in the past, in several platforms, the controversy it generated during these last years, the name change, and the exit of one of the most brilliant minds that shaped the way VR is to be experienced by us all, from the company, I have come to a sad conclusion: Meta is no longer to be trusted with our account data. It is with a very heavy heart that I do this. I love my Quest 1, it is (almost) everything I have wanted a VR headset to be, and I'd love to use it forever and ever (particularly, with Developer Mode on), but my fear of Meta misusing my auth data is currently overwhelming my feelings for the device. It's been a wild and nice ride. Thank you everyone who supported me by playing my only published (sideloaded) VR app, and I wish you guys who will accept Meta's terms the best with your devices, old and new. Me? I'm out for a different way to experience VR - that is, unless Meta decide to change things regarding its current account issues. --------------------------------------- I would like to leave this thread open for other people to comment on this, and to listen to your opinion about this issue, if you're inclined to do so. I will not be able to answer, of course, since I won't have a Meta account to do it. But anything you wish to say here, I will make sure to read it for as long as I'm able to.
Uploading PWA (Progressive Web Apps) builds to the Meta Store
Hello! I'm currently trying to upload a PWA to the Meta Store. Uploading a build manually is deprecated so I'm using the ovr tools. When trying to upload a build, it responds with an error stating that: Application XXXXXXX is not configured as a progressive web application ... How do I setup my application to be a PWA? I see nothing where the guide says there should be something. I found a guide stating that I already need an application on the Meta Store firstly, before I can upload a PWA, but that just doesn't make sense to me. Hope for some help, thanks! What I see:: Guide screenshot:
