ERR_CLEARTEXT_NOT_PERMITTED
Hi. I'm working with Unreal Engine 5.3 and Meta Quest 3. I'm having the following error message when using a web browser within UE5 and connecting to an HTTP url. ERR_CLEARTEXT_NOT_PERMITTED Do you know how can I enable the use of cleartext http traffic? Is it somewhere in the MetaXR Plugin or MetaXRPlatform plugin or would it be somewhere in UE5 Settings or do I need to modify some AndroidManifest.xml somewhere? I found that someone asked something related here: https://communityforums.atmeta.com/t5/Quest-Development/Having-issue-with-setting-Cleartext-HTTP-traffic-for-development/m-p/777427/highlight/true Also found some info for Android development here: https://www.repeato.app/how-to-resolve-cleartext-http-traffic-not-permitted-error-in-android-8-and-above/ Any help would be greatly appreciated!484Views0likes1CommentHow 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?SolvedExploring ChatGPT Integration for VR UI/UX: Has Anyone Tried It?
Hi everyone, I'm currently experimenting with ways to integrate conversational AI (like ChatGPT) into VR environments to enhance user onboarding, contextual help, or dynamic NPC interactions. I’m working with Unity and targeting Quest 2/3. My goal isn’t to run the model locally, but to connect to external APIs (e.g., OpenAI) via secure HTTPS requests — ideally triggered by user input or voice in immersive menus. I’d love to hear from other devs: Have you tested anything similar in a VR context? What are your thoughts on latency and user flow when connecting to external services in VR? Any advice on best practices for handling text responses (display, formatting, user focus)? Are there any sample projects or SDKs that play well with Meta Quest platforms for this use case? This is still a prototype phase for me, but I believe natural language interaction could really improve the way users explore VR content — especially for onboarding or educational apps. Looking forward to your insights!102Views0likes3CommentsApp Distribution Upload Issues: DevPost
Hi, Posted this earlier in the general Forum and discovered this may be a better place for help. I'm attempting to Upload a build to my Alpha Channel via the Meta Quest Developer Hub but it keeps failing. Below is the Error message: Error: An unexpected error occurred {"cliErrorType":"UNEXPECTED_ERROR","cliErrorMessage":"File or directory 'D:\\**\\' was not included into executable at compilation stage. Please recompile adding it as asset or script." I'm assuming this means I need to add the Directory and or filepath to the assets within my Unity Project but I'm not finding much in the way of how to actually do so. Please let me know if anyone has any ideas of how to do so or if you've encountered this error and found a solution. Below is a screenshot of the error message. The App is developed for PC and the build is for the Rift S. Once this is all good I plan on making a Quest Build as well. Best regards,Solved2.9KViews1like7CommentsMRUK not found despite it being created...?
I'm currently using Quest 3 v62 (now v63) and Unity 2022.3.10f1. Working on a random spawn mechanic in the MR environment where objects can spawn on the ceiling. The feature worked fine when I tested it on Unity Playtest, but once I built it on the standalone Q3 (or simply hooked it up with a quest link), the scene could no longer be implemented. The room setup does indicate that I have my tables and walls, but there's no ceiling. I presume the Spatial data didn't transfer properly (I did write a script to grant permission to Q3 for spatial data, and clicked the Permission Requests On Startup) I have no idea where it all went south. Any ideas?1.7KViews0likes2CommentsFAIL_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.Solved5.8KViews0likes16CommentsMQDH can not keep sync alive for more than 3 seconds...
Hello!. I hope all you to be fine .. I'm experimenting some strange behaviour as follows: 1) I open MQDH and it recognizes my Quest 3, but keeps "Unauthorized" 2) I check my Quest 3 and there is no popup message... so, make some reboot here and there.. and then i got the popup again.. 3) I have allowed the connection. 4) MQDH enters debug mode for ADB, that's cool! ....3 seconds later... 5) MQDH returns with the message "Unauthorized" and exits the debug mode. Also it says in red: "Failed to refresh user on device X" My Specs: Windows 11 Ver. 10.0.22631.4317, 64-bits MQ3 built in package USB-C Cable . MQDH Version 5.1.0 MQ3 is with latest updates. I have enabled debug mode with Meta Horizon App from my Mobile. Any help will be very appreciated. Mikeh568Views0likes2Commentsnot able to purchase games with prepaid mastercard
I purchased a Pre-paid Mastercard and it will not me buy a game. The card has enough funds, is activated and I made sure I put the information from the card in into the Meta store correctly. I have tried both my phone and computer but neither work. It keeps telling me "GraphQL server responded with error 1353048: Sorry, your payment method was declined. Try updating or using a different payment method." If anyone could help me with this it would be very appreciated.1.7KViews1like4Comments