Solved

After building our metaverse application and not having tested in a while, it seems to not be running and instead crashing on each launch. Oculus firmware 50 seems to be the cause of this. We are using 2021.3 LTS and IL2CPP with Arm64. The error is a Sigabrt Signal 6 Code -1 Fatal Exception Java Lang Error. The app seems to be working with Mono Arm7 but only when it doesn't have more than like 4 scenes. I hear that firmware 50 may have Android 12 and was released for early access users. We've tried everything in the book to fix this, and apparently the performance isn't going to be the same either even if we do get it to run. We are going to update to Unity 2022 to see if this fixes anything but we've been spinning our wheels like crazy. Please let me know if you have any ideas as to why it is suddenly crashing without explanation.

Hello!I'm implementing a feature with Unreal Engin that uses Spatial Anchors. I'm saving them in the Cloud using the OculusAsyncSaveAnchors function which works perfectly fine on Quest 2, but on Quest 1 I am always getting an Error there with code -1000 which does not give any information.So I wanted to ask if saving Spatial Anchors in the cloud is even available on the Quest 1 and if so is sharing Anchors available as well?(In the Documentation it's often stated as new Quest 2 features so I wasn't sure and the local saves also work fine)Would be great if you could help me clarify this.

I'm making a VR app, I can only test it on my dev account, if I test IT using my personal account the Meta Avatar doesn't load and the Entitlement Check returns me an error.We don't want to make the app public anyway, so is there any way to use it without having to add each user as a tester?

Problem:- Meta Quest Developer Hub (.apk built from Unreal Engine 5.0.3) crashes upon launching.- App launch was working fine 6 hours before my Oculus was left switched on unattended (went to bed, woke up, did nothing to change anything and it didn't work anymore. was able to launch + cast prior).- Used an old working .apk file to test and it crashes upon launching as well.Have tried to troubleshoot but to no avail:- factory reseting oculus + changing a new oculus set- reinstalling several backed-up .apk files which used to work prior to sleeping- repackaging .apk from my different backed-up unreal projectsImported a sample VR template from UE5 and packaged it, .apk app launches successfully on Oculus. However, migrating my project file into the new template causes the new .apk to fail launch.Rebuilding my entire game from VR template is too time consuming.Any solutions/troubleshooting suggestions would be greatly appreciated. Please send help!

I can't figure out how to get around this issue. I have generated a keystore file and successfully used it to compile my app, so my app is signed, right? It's in my Unreal settings, with the Keystore, the user name, and password. The Keystore is in the Build folder, it's a "Shipping" build. UE4 4.26 compiles the app successfully. But when I use the Oculus Platform Window to upload it, after it goes through all of the upload stuff, it stops and tells me I need to Sign my App. It's a free game, so I don't know why it needs this level of security at all. :p 

I am having issue uploading images to the Oculus App Lab App Submission > Assets section. I have consistently got an error that says “Unsupported Image Dimensions” while the dimensions/resolution have been verified multiple times. 

So I've nearly got the Avatars streaming correctly using Photon Pun, but I get these errors when there's another remote avatar in the scene. It seems like a server connection issue (code: 400) but I'm unsure what could be happening, since I'm successfully connecting to the server in both instances, and the gray, unskinned avatar is still rendered and follows the players.My current theory is it's because I'm running the project in my Unity Editor while also running a build on my headset that I uploaded as an Alpha release to the channel. What I've noted is that the user ids' are different between these two instances, despite being the same app/project. Unfortunately, I don't have another headset to test this.Does building and pushing to the store change the app id received? Or is there something else I'm missing in the Avatar SDK? 

I tried to use the Ray Interaction feature of the Oculus Integration SDK to interact with Text Mesh Pro UI, but it doesn't work. The raycasting passes through the UI surface. However, when I used the same UI surface with the Ray Interaction feature of OpenXR, it worked fine.I'm wondering if the Text Mesh Pro UI can be used with the Ray Interaction feature of the Oculus Integration SDK. Are there any specific settings that need to be configured?Any help would be greatly appreciated.

Hello,I am trying to open the Oculus Quest 2 browser from my Unity application, to display a web page.This was working reliably, but suddenly stopped with no app changes. We believe it could be due to a software update on the Quest.We do:Application.OpenURL("<url>");And that used to take the user to the browser page and leave the app. This was exactly the flow we needed. Now, the app flashes black for half a second, and quickly comes back in focus. And when the user eventually quits the app manually later, then only does the browser open.From Android Logcat, we are getting:Error SecurityUtil Failed to verify identity of calling application for app launch flow. Bundle is missing handshake binder! Now, it sounds like there's a solution! Bundle is missing handshake binder, that sounds promising. But I can't find what a handshake binder is or how to add one. Anyone would have any hint?Thank you

I tried to use Quest Pro with Unity via Link, but when I imported Oculus Integration, the following error occurred. "DllNotFoundException: AudioPluginOculusSpatializer assembly:<unknown assembly> type:<unknown type> member:(null) ONSPAudioSource.OnBeforeSceneLoadRuntimeMethod () (at Assets/Oculus/Spatializer/scripts/ONSPAudioSource.cs:50)"I used the Unity Editor version 2022, Oculus Integration version 51, and Windows 11 x64.Please let me know the solutions to fix this error.Thank you in advance.

For about the past 5 days, our users from all organizations have not been receiving any updates on their subscribed applications, despite everything working smoothly before. Do you happen to have any insight as to what changes may have occurred on App Lab?

I released a new update on the alpha channel for my game. It has been in the Malware Review Test for about a whole 24 hours now.  Anyone else having this issue?

it veri goooood 👏 

Hi,This started happening since last week. The development APK build launches through RenderDoc OK, but while the application is loading, Renderdoc Meta Fork returns this error message:I've tried Renderdoc Meta Fork versions 39.2, 39.6,40.1,44.1,50.1 and 51.1. It seems to be quite random when it appears. The only way to fix it at the moment seems to be to keep installing various versions on the Quest2 until the error doesn't appear anymore. Sometimes the ADB and Renderdoc log/dmp files get updated during a crash, examples are shared here:https://drive.google.com/drive/folders/1-z4-VxMAwEnXskJ6hnngPlxAIaIWNVKC

I thought I read that Oculus won't allow us to collect income/payments for app lap apps outside of the Oculus platform without some kind of agreement with them. But I can't seem to find that, and I just now ran across this post that says we can sell keys without giving any revenue to Oculus: https://developer.oculus.com/blog/oculus-distribution-channel-guide/ We're building education apps and want to be able to sell "bulk" licenses to schools, for example, in addition to sales to individuals on app lab. Can somebody point me to the right answer/resources/docs on this issue? Thanks in advance!

Hello,Enabling the GPU metrics recording on Perfetto via MQDH doesn't seem to work anymore. Nor does enabling render stage traces.I've tried running perfetto from adb with track_event as data source on a custom text config (while ovrgpuprofiler -r runs on another shell session), which used to work, but that also not working as well.I'm under the impression that those trace sources stopped working a few weeks ago. By the way, my device is on firmware version 50163300257300150 (incremental number).Is this a known issue?Cheers,

When I upload my file I won't to get a test to run on then be on the beta channel it just has a blank space and wont do a test. Anyone know how to fix this? 

Meta rejected all my admin verification requests because they couldn't read the docs I sent them (multiple times with different lighting conditions (artificial and natural) and resolutions).They also suggest trying to verify as an organisation or with another admin account. But I'm the only admin, and I'm the only person that works on the project. Is it possible to release an app on AppLab without being an organisation? Like in the way you release apps on Apple's AppStore. Because right now, it seems like you have to have an organisation to be able to drop something on the AppLab (which is, I guess, supposed to be a little bit more friendly for indie devs and experimental projects).

Hi Team, Thank for you for hard work! Meta Quest Browser has been awesome to develop with.  I'd like to report a bug, or at least an oddity.. I've noticed that the Meta Quest Browser enforces sandboxed IFrames to have "allow-same-origin" be toggled, or else VR content cannot load and with threejs (webxr) specifically, it will crash the browser! This behavior does not happen on Chrome, though I am using a chrome plugin to use "VR" on my local workstation, so its not exactly a 1-to-1 test.  To reproduce this issue, create a simple Iframe with threejs/babylonjs webxr content in the srcDoc attribute: This below example WILL work.   <iframe scrolling={'no'} style={{ display: 'block', border: 'none', margin: '0px', height: '100vh', width: '100vw' }} sandbox="allow-scripts allow-same-origin" title={scene_uuid} srcDoc={sceneJsData} hidd

I've been getting an array index error whenever I try to use the Oculus XRHand Component - required for hand tracking / and body tracking. I've posted about it on the GitHub repo, and had one person confirm a similar issue, but so far no one else seems to have the problem(?)https://github.com/Oculus-VR/UnrealEngine/issues/247 Is anyone using the Oculus XRHand Component in the new engine build without issue? Hand Sample / HandPoseShowcase sample maps throw the error / crash the editor.EXAMPLE:Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:H:\GitHub\UnrealEngine\Oculus\UE5\UnrealEngine\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 763]Array index out of bounds: 1806 from an array of size 24When I open the sample project: \UnrealEngine\Samples\Oculus\HandSample\HandSample.uproject I can play in Viewport / Simulate without issue, but if I VRPreview or build a standalone game I get the array error as soon as the engine registers the he

Everything goes fine, it connects, even gets to the last screen where you plug in the headset, I click ok on the Mac and ok on the headset to allow the connections, and then nothing. The headset doesn't connect or show up and I have to do the connection all over again in an endless loop. Uninstall, factory reset etc etc. Does anyone have any idea how to resolve this?The last version of Meta Quest Dev Hub was working just fine for me, same Mac, same headset.

Not able to find movement SDK in Oculus Integration SDK v46. Am I missing something or its actually not shipped yet?

Hi, I just upgraded to version 9817240250200320 on an oculus quest pro. Since then certain MRTK functions are not working any more, that have been previously working. I narrowed the problem down to the implementation of IMixedRealityPointerHandler. In some cases I want to filter for near interaction only, by checking that the data handed over is a SpherePointer. This does not seem to work any more:Example:public class RemotePhysicsController : MonoBehaviour, IMixedRealityPointerHandler{/// <summary>/// Get the interaction grabbable./// </summary>public void Awake(){gameObject.AddComponent<NearInteractionGrabbable>();} public void OnPointerDown(MixedRealityPointerEventData eventData)    {        // We only want to interact with near.        SpherePointer pointer = eventData.Pointer as SpherePointer;        if (pointer == null)            return; &nbsp

what do you think my pfp is? i'll solve this when Someone gets it right

Spent a god awful amount of time trying to get eye tracking working to no avail.  tl;dr: it seems like there's an issue with permissions generated in the manifest generation stage somewhere.inspired by https://forums.oculusvr.com/t5/Quest-Development/Movement-SDK-features-fail-to-start-on-Quest-Pro/td-p/994198 Repro and debug info:Unity V2021.3.12f1Oculus XR Plugin V3.2.1Oculus Integration v46.0OVRCameraRig - Quest Features (Eye Tracking Supported)OVRCameraRig - Permission Requests on Startup (Eye & Face)Test Scene: Assets/Oculus/SampleFramework/Core/DebugUI + two cubes with OVREyeGaze enabledFile -> Build Settings -> Project Settings -> XR Plugin Management -> Oculus -> Android icon -> Quest Pro checked Summary:Looking at the manifest in the generated apk (used Android Studio to inspect), I see that face tracking tags are included but eye tracking tags are missing.Additionally, when starting the app with these settings the face permission