Forum Widgets
Recent Discussions
How to obtain the user token using the Meta XR Platform SDK
I currently need to link the player's Meta account to our game using the Unity Meta XR Platform SDK for login purposes. After passing the application permission check, the player's ID can be obtained through the Users.GetLoggedInUser() method. However, the Token cannot be obtained using the Users.GetAccessToken() method. This method always returns an empty result. Could you please tell me if I have not configured something correctly or if there is any missing step?Solvedluolikong_f4 months agoExplorer25Views1like1Commentvirtual desktop + voicemeeter?
i cant get it to work, ive tried all the tutorials on youtube, and ive enabled voicemeeter mode on virtual desktop streamer but i cant get music playing through my microphone. i dont want to go back to quest link because its so bad, but i really want to get this to work. i got it to work once but there was a really bad echo. ive tried voicemeeter potato and banana, but neither of them work for me. i dont know what im doing wrong.Solvedantarish44 months agoHonored Guest2.3KViews0likes2CommentsAdvertising Account Restrictions
I have been trying to fix a problem that I have with an ad account since last night. I have sent several messages but don't have a response. I have two business pages, My assistant used to run ads on the first page and never reported any issued to me about the ad account. I have been working on the new page, and checked everything when I was creating an ad account. I went through a good number of meta blueprint courses to make sure, I am doing everything right. I tried running an ad last night and found a problem with it running. when I looking into the ad setting, it set account restrictions. I checked and all previous accounts from my personal and other business page looked ok, when I started digging deeper, It showed account restrictions on two of my ad accounts. However, when I looked into the ad manager for those accounts there were no rejected or restricted notices on any of the ads. however on top of the page, it showed the account restriction. When I click on the more details to find out about it, the page is clear with no information. Can I ask someone to help me resolve this problem? ThanksSolvedSagharDara7 months agoExplorer1.7KViews1like8CommentsInteraction SDK Grabbing Issues Unreal Engine 5.5
Hi to everyone, I would like to have some help with this issue, I've been trying to use the Interaction SDK in UE 5.5, but I saw on the page that they changed a couple things, and now even if I follow step by step any tutorial, I can't make the grabbing component work, can someone please assist me?SolvedARSSIO9 months agoHonored Guest2.2KViews0likes7CommentsHow to Hide Controller Models ?
Hi, I am a developer and am wondering how to disable the controllers being shown when using the Building Blocks in Unity. Can I use the Controller Tracking Building Block but hide the Quest controllers? I'm also using Networked Avatars, and want to pick up things using the avatar's hands, and not see the controller in the avatar's hands. Is this possible? It seems that documentation is really lacking when it comes to developing for the Quest. Hell, there's one small page on Building Blocks (https://developers.meta.com/horizon/documentation/unity/bb-overview) that isn't much of a deep dive at all. Am I missing something? Is there a page that has more detailed documentation? After spending quite some time on these forums, google, and YouTube it seems like a lot of others have questions too. Thanks.SolvedPaulBearerJr2 years agoProtege1.7KViews0likes1CommentKeyword search not working from headset or mobile platforms
After the App Lab and the Main App store were combined, it was then possible to enter keywords as part of the metadata for my app. One of my keywords is “breakout”. When I search for “breakout”, I only get 1 match, and that app is not “Close Encounters” or "Close Encounters Demo". Do the keywords take some period of time to kick in? Also, when I scan the list under Apps->Games->See All, I never see my app. I’m wondering if I have done something wrong. My app appears to be invisible to the general public!Solvedlarry.roy8902 years agoProtege2.7KViews2likes9CommentsCan't log in to support
Hi, I can't login to the Oculus support center page: https://oculusdevelopers.zendesk.com/hc/en-us When I click on "log in with oculus" this pops up for a second (see first image) then it loops back to the login page (second image). Clicking "cancel" reloads the page. FYI I have a dev account and can access the develper dashboard.SolvedINFAMUSENTERTAINMENT2 years agoExplorer1.5KViews1like3CommentsFAIL_FORBIDDEN_PERMISSION Developer Hub error READ_PHONE_STATE Error
I have no other errors besides this one when I upload my build to the alpha production stage. The error says this: FAIL_FORBIDDEN_PERMISSION The upload could not be completed because your application contains the following Android permissions that are not supported: - android.permission.READ_PHONE_STATE Please remove the following permissions and upload your application binary again. The log says this: 2024-08-03T21:58:36.097Z [DEBUG] Run args: {"appId":"26165759013071717","apkPath":"C:\\Users\\rcper\\OneDrive\\Desktop\\Gorilla Flag First Version\\First Version.apk","channel":"ALPHA:quest2only|questproonly|quest3+","draft":true,"excludeAddons":false,"inheritAssetFiles":false,"isODH":true,"uploadFromEngine":false,"token":"(removed)","uploadConcurrency":null,"platform":"ANDROID_6DOF","disableProgressBar":true} 2024-08-03T21:58:36.367Z [DEBUG] Server log: {"app_id":"26165759013071717","client":"ODH","log_level":"DEBUG","event_name":"COMMAND_PARAMS","stack_trace":"at Object._log (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat Object.debug (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\nat processTicksAndRejections (node:internal/process/task_queues:96:5)","extra":"{\"appId\":\"26165759013071717\",\"apkPath\":\"C:\\\\Users\\\\rcper\\\\OneDrive\\\\Desktop\\\\Gorilla Flag First Version\\\\First Version.apk\",\"channel\":\"ALPHA:quest2only|questproonly|quest3+\",\"draft\":true,\"excludeAddons\":false,\"inheritAssetFiles\":false,\"isODH\":true,\"uploadFromEngine\":false,\"token\":\"(removed)\",\"uploadConcurrency\":null,\"platform\":\"ANDROID_6DOF\",\"disableProgressBar\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.98.0.000001\",\"compatibility_version\":2,\"session_id\":\"26165759013071717_2024-08-03T21:58:36.095Z\",\"command\":\"upload-quest-build\",\"app_id\":\"26165759013071717\"}","platform":"ANDROID_6DOF","cli_version":"1.98.0.000001","session_id":"26165759013071717_2024-08-03T21:58:36.095Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":271} 2024-08-03T21:58:37.552Z [WARN] 🟡 WARNINGS: • Quest 1 support is automatically disabled for apps created after 04/30/2024. Please refer to this post for more details: https://developer.oculus.com/blog/changes-coming-quest-1-2023-meta/ • Your manifest includes the following permissions restricted by Oculus: - android.permission.WRITE_EXTERNAL_STORAGE - android.permission.READ_EXTERNAL_STORAGE - android.permission.READ_MEDIA_AUDIO - android.permission.READ_MEDIA_VIDEO - android.permission.READ_MEDIA_IMAGES - android.permission.ACCESS_MEDIA_LOCATION - android.permission.READ_MEDIA_IMAGE Please remove these permissions if they are not needed by your application. If they are needed, you must include justification in the “Notes for the Reviewer” field when submitting your application for review. Failure to provide justification will result in the rejection of your application. • This app contains both 32-bit (armeabi-v7a) and 64-bit (arm64-v8a) libraries. This consumes extra storage and increases download times. Consider updating your build to target 64-bit only. 2024-08-03T21:58:37.552Z [ERROR] Server log: {"app_id":"26165759013071717","client":"ODH","log_level":"ERROR","event_name":"UPLOAD_PREVALIDATION_FAILURE","stack_trace":"at Object._log (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat Object.error (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\nat processTicksAndRejections (node:internal/process/task_queues:96:5)","extra":"{\"errors\":[\"The upload could not be completed because your application contains the following Android permissions that are not supported:\\n - android.permission.READ_PHONE_STATE\\nPlease remove the following permissions and upload your application binary again.\"],\"warnings\":[\"Quest 1 support is automatically disabled for apps created after 04/30/2024. Please refer to this post for more details: https://developer.oculus.com/blog/changes-coming-quest-1-2023-meta/\",\"Your manifest includes the following permissions restricted by Oculus:\\n - android.permission.WRITE_EXTERNAL_STORAGE\\n - android.permission.READ_EXTERNAL_STORAGE\\n - android.permission.READ_MEDIA_AUDIO\\n - android.permission.READ_MEDIA_VIDEO\\n - android.permission.READ_MEDIA_IMAGES\\n - android.permission.ACCESS_MEDIA_LOCATION\\n - android.permission.READ_MEDIA_IMAGE\\nPlease remove these permissions if they are not needed by your application. If they are needed, you must include justification in the “Notes for the Reviewer” field when submitting your application for review. Failure to provide justification will result in the rejection of your application.\",\"This app contains both 32-bit (armeabi-v7a) and 64-bit (arm64-v8a) libraries. This consumes extra storage and increases download times. Consider updating your build to target 64-bit only.\"],\"time\":549,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.98.0.000001\",\"compatibility_version\":2,\"session_id\":\"26165759013071717_2024-08-03T21:58:36.095Z\",\"command\":\"upload-quest-build\",\"app_id\":\"26165759013071717\",\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.98.0.000001","session_id":"26165759013071717_2024-08-03T21:58:36.095Z","binary_id":"","duration":549,"is_patch_upload":0,"duration_since_session_start":1456} 2024-08-03T21:58:37.793Z [ERROR] :cross_mark: ERROR: • The upload could not be completed because your application contains the following Android permissions that are not supported: - android.permission.READ_PHONE_STATE Please remove the following permissions and upload your application binary again. 2024-08-03T21:58:37.793Z [ERROR] Server log: {"app_id":"26165759013071717","client":"ODH","log_level":"ERROR","event_name":"USER_ERROR","stack_trace":"UserVisibleError: • The upload could not be completed because your application contains the following Android permissions that are not supported:\n - android.permission.READ_PHONE_STATE\nPlease remove the following permissions and upload your application binary again.\n at C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\n at processTicksAndRejections (node:internal/process/task_queues:96:5)","extra":"{\"error\":\"• The upload could not be completed because your application contains the following Android permissions that are not supported:\\n - android.permission.READ_PHONE_STATE\\nPlease remove the following permissions and upload your application binary again.\",\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.98.0.000001\",\"compatibility_version\":2,\"session_id\":\"26165759013071717_2024-08-03T21:58:36.095Z\",\"command\":\"upload-quest-build\",\"app_id\":\"26165759013071717\",\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.98.0.000001","session_id":"26165759013071717_2024-08-03T21:58:36.095Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":1697} Thank you for your time.SolvedGamerRoman222 years agoExplorer5.8KViews0likes16CommentsMeta update v68 & OpenXR - xrEnumerateInstanceExtensionProperties fail to return any valid extension
A critical issue has arisen with the recent update of the Meta Quest Link application to version 68.0.0.433.361. In summary, all of our applications based on Khronos OpenXR and Unreal Engine 4.27.2 can no longer be run via Link. This means that the vast majority of our customers can no longer access our applications. Additionally it prevents our Unreal Engine developers from being able to use tethered Meta devices. This issue has been confirmed for Meta Quest 2, 3 and even Rift S devices. This issue has been confirmed in vanilla Unreal Engine projects also. We have traced the failure to the OpenXR runtime layer. OpenXr API calls such as xrEnumerateInstanceExtensionProperties fail to return any valid extensions, which prevents the Unreal Engine being able to communicate with the headset. We believe that other people may be having the same or similar issues with the recent update: https://steamcommunity.com/app/1849250/disussions/0/4515506358400756962/ https://www.reddit.com/r/oculus/comments/1e6lq00/comment/lecf5bu/ https://communityforums.atmeta.com/t5/Get-Help/Open-XR-Toolkit-was-broken-with-v68-Oculus-Link-code/td-p/1223235 Are you aware of this issue? Are you looking into a resolution or is it an intended change? Repro Steps: Create a VR template project using Unreal Engine 4.27.2. Make sure the active OpenXR runtime is set to the Oculus runtime. Observe that the Unreal Editor will not let you run the project in VR with a Meta headset connected via Link. (Option is greyed out because it cannot detect the headset.)SolvedMetaLoc2 years agoExplorer5.8KViews12likes8Comments
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device