Google Play Requiring API Level 34, Quest 3 on API Level 32
Starting August 31st Google Play apps are requiring API Level 34. My company is shipping an app the first week of September so we are required to meet this requirement, but the quest is only on API Level 32. I'm surprised I'm not seeing more people talking about this am I missing something or are quest apps just not going to allowed on google play because of this?API Error - Can't upload PCVR Rift build via Meta Quest Developer Hub
Hello! I need some help from Meta's engineering team. I am unable to upload a PCVR (Rift) build of my VR game via the Meta Quest Developer Hub (MQDH). I have a working VR app that runs just fine on PC via Quest Link or AirLink (created via Unity 2022 LTS + OpenXR). However, when I try to upload my app build via MQDH, I get a non-descriptive "API Error" and it points me to a log file. I have attached a screenshot of the error below. I can't attach my log file here because it contains sensitive information, however I am happy to provide it to Meta privately (please let me know the best way to do this). Some additional context: I am using Unity 2022.3.7f1 LTS and I am using the OpenXR runtime via Unity's XR Plug-in Management system. I have both a Quest version and a Rift version of the same app. If it matters, I have *not* imported the Oculus Integration because I am using the new OpenXR runtime and Unity's XR Interaction Toolkit, as is recommended when using OpenXR. The Quest version of my app uploads just fine via MQDH and passes all automated tests. But when I attempt to upload the PCVR build for my Rift version of my app, I get an "API error". Could someone from Meta please let me know what to do in order to successfully upload a PCVR app build for the Rift version of my app? I am happy to provide you with my log file also. It is very important that I support both Quest and PC. Thank you!
Subscription API Test Fail
Hi, I am unable to test IAPs. I have followed this guide https://developers.meta.com/horizon/documentation/unity/ps-iap-test My organisation is verified, I have a test user, which can be granted test add-ons. And I can consume them using the API on my server. However, I have tried multiple times to buy a subscription through the horizon mobile app, logged in as the test user. I used the card details provided in the documentation above, and also added the cards using the test user menu "manage test cards" modal. I always get the same message, in the test menu and in the mobile app purchase. Not sure what to try next.api error on MQDH portal
The app is not getting published for Alpha release. It's showing api error on MQDH portal while submitting the app. It's getting uploaded if the size is less than 500 mb. I have also checked the forum but couldn't able to find the answer. is there anyone also faced similar issue ?MQDH / Developer Dashboard - Server Error - API Error - No Tests Ran on Build
I am having a number of issues with Meta Quest Developer Hub and Developer Dashboard. For the past three days I have been unable to upload a build through MQDH due to a few different errors. I am using the latest version of MQDH. When uploading a build I either get an API_ERROR, ECONNRESET error, or PROCESSING_ERROR "please try again later". Looking at the logs it said server error, attempting to try again, and does this over and over. It doesnt seem to be an issue with my actual build, or manifest or anything that I am able to solve on my end. Have tried reinstalling MQDH or switching the adb file path to match unity. After repeated attempts failing through MQDH I decided to try using the OVR Platform Utility Tool. I was able to upload my .apk with an OBB file, though I received multiple server errors in the process. After about and hour and a half the upload process finally succeeded through the server errors and I am able to see my new build in developer dashboard inside a new release channel. My new issue is that the new build uploaded has not yet gone through the automated testing. I uploaded the build over 16 hours ago. Dashboard still says "No test runs were found to be associated with this build." Because of this I cant actually install and play this new build. And with both MQDH and Dashboard causing issues I am at a complete standstill on my project. Is there some sort of server issue on Metas side that is causing this? Any assistance is greatly appreciatted
