OSC/WebSocket/MQTT to Quest
Hi there, I'm trying for a few days to have something working on UE4.27 and I'm hitting a wall. I've made a blueprint where i'm able to receive OSC input data from a remote laptop to a UE4.27 app that then triggers an event (for now print something or play a specific audio cue). It works flawlessly on UE4.27 but as soon as I load the project onto the quest and send that same OSC input data it crashes the app on the Quest 2. I tried different ports, data formats but still the same behavior without much logs to learn from which make me wonder if the Quest forbids such incoming IP communication ... could someone confirm whether or not Oculus Quest accepts remote information (regardless of the protocol used). Maybe I'm missing something in the settings somewhere but I couldn't find much information about it. Thanks for your response
High crash rate of GameActivity onPauseNative
In my app available on the store, data analysis has frequently shown the occurrence of this crash issue: 1. Crash Type: App Not Responsive Crash Reason: oculus:android_anr:com.google.androidgamesdk.GameActivity.onPauseNative 2. Crash Type： App Not Responsive Crash Reason：oculus:android_anr:com.google.androidgamesdk.GameActivity.onSurfaceDestroyedNative I suspect the issue occurs during user IAP (In-App Purchase) because I occasionally experience a crash when canceling a purchase.
Problem with implementation of XRInputSourcesChangeEvent on Quest browser
Hi, I'm working on the development of a WebXR application and I've recently noticed an issue when the input controllers are temporarily lost and "reconnected". The reconnection triggers a XRInputSourcesChangeEvent event with an "added" property listing XRInputSource objects associated to each controller that is reconnected. These XRInputSource objects are supposed to have a gamepad property but it seems that this property is not set correctly (it's null) when a controller is reconnected. The problem doesn't occur the first time the controllers are detected after the initialization of the XRSession. The problem isn't reproduced on a different browser (wolvic). Environment: - Headset: Meta Quest 3 - Version: 64.0.0 Expected behavior: XRInputSourcesChangeEvent should provide an "added" property listing XRInputSource objects with a properly initialiazed gamepad property when a controller is "reconnected". Any idea for a workaround until a fix is implemented would be appreciated.
FIX YOUR LINK SOFTWARE
PCVR with Link is the absolute worst software I have ever used almost daily I will be in iRacing and the Link glitches out, the entire community knows it's trash and always suggest using Virtual Desktop. I Have recently purchased a Bigscreen Beyond 2 headset and will never use Quest again constant software updates and glitches. learn how to code software that doesn't suck.
v79 Dialog-Related Crashes in Android Settings
Since the v79 update, various dialogs in the Android Settings app are no longer accessible and crash the Android Settings app when opened. This includes, but is not limited to, the following: WiFi & Internet -> Private DNS Accessibility -> [ANY SERVICE] -> Turn On System -> Developer -> Wireless Debugging -> Pair with Pairing Code The following error is visible in LOGCAT: FATAL EXCEPTION: main Process: com.android.settings, PID: 2626 java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity. at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor(AppCompatDelegateImpl.java:926) at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor(AppCompatDelegateImpl.java:889) at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:772) at androidx.appcompat.app.AppCompatDialog.setContentView(AppCompatDialog.java:99) at androidx.appcompat.app.AlertController.installContent(AlertController.java:232) at androidx.appcompat.app.AlertDialog.onCreate(AlertDialog.java:278) at android.app.Dialog.dispatchOnCreate(Dialog.java:436) at android.app.Dialog.show(Dialog.java:325) at androidx.fragment.app.DialogFragment.onStart(DialogFragment.java:973) at androidx.fragment.app.Fragment.performStart(Fragment.java:3173) at androidx.fragment.app.FragmentStateManager.start(FragmentStateManager.java:625) at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:290) at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1938) at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1841) at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1778) at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:564) at android.os.Handler.handleCallback(Handler.java:958) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:218) at android.os.Looper.loop(Looper.java:310) at android.app.ActivityThread.main(ActivityThread.java:8250) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978) This is a regression from v78 and prior versions, where these dialogs all worked as expected.S2S REST request not working on some users
So I have a backend for my game and I want to call some S2S requests to get user's data, purchaes and verify purchases. I am using the end point https://graph.oculus.com/${APP_ID}/viewer_purchases to get user's purchases. I provide access_token, user_id, and fields. Just like it mentions in the documention for IAP here https://developers.meta.com/horizon/documentation/native/ps-iap-s2s. The requests are working just fine with some users, but sometimes i enter a user id and get this error: here is an example of it working: if i just enter a random user id: (translation: it says thats an invalid user id) This is not just for this user, it happens for many users. Also it is happing for other requests like https://graph.oculus.com/${USER_ID} to get verified org_id and in consuming and verifying requests. I know that some of these requests dont work for meta test users (users that meta itself uses to test the game) but these users are real players. If anyone has any idea why this is happening please let me know. Side note: the consume_entitlement request also doesn't work sometimes where it throws a 500 is_transient error with code 2 but it still consumes the purchase correctly. weird...
