Customers cannot "GET" our app (App Lab)
From what I can understand, a Quest App is available by the app id link before being reviewed. This allows users to install the app from a direct URL rather than the AppStore. Our app is viewable on PC by the App Id link, and everything looks fine, except there is no GET button. Also, when the same URL is viewed on the Quest, a 404 error is displayed. Is the App Lab broken, or am I missing a setting somewhere? Now that the App is in a review state, there are no settings available to us for change. Strangely, the URL is viewable on PC but not the Quest. We want our app to be available to our users, precisely many schools anxiously waiting to use our app. Our previous app worked with Google Cardboard, and now the schools are migrating to the Quest. We are unable to give them our app because of this issue. We need to have our app used by students before the school year is complete. By not having this app available to students, this delay is robbing children of an educational experience that could shape their future with a career in technology.
OCULUS_PLATFORM__APK_PACKAGE_NAME_ALREADY_IN_USE
Hi, I am trying to deploy a Meta Quest App to the Meta Store. The first submission was rejected, so I am trying to submit a new one, but when I try, I get the following error: OCULUS_PLATFORM__APK_PACKAGE_NAME_ALREADY_IN_USE The funny part is when I try some other name, I get a new error saying that I am trying to use a new package name, and I must use the previous name. Meaning the previous name that is giving the error of package name already in use So maybe someone has had the same issue. I am totally blocked because of this, because I can not submit the new version of the app. Thank youAppLab Approval times
Hi - I submitted an app on Feb 17, 2022 ... after 4 weeks i received a change request for the artwork. I re-submitted the next day after changing the artwork, and its been 4 additional weeks now (8 weeks since original submit) and the app just sits "in review". Is this normal? Is there a way to contact the applab review team or log a ticket? I have a community eager to test drive my app and have very little to tell them. Any help appreciated. Thanks.Unable to upload to AppLab. Error This APK contains libInteractionSdk.so and targets Android SDK 31
I am trying to upload a build to AppLab and getting error "This APK contains libInteractionSdk.so and targets Android SDK 31. This is currently unsupported; please set the target Android SDK to 29 or 30, or remove the Interaction SDK and try again." I am using Unity 2022.2.6f1 and Oculus Integration v50 (also tried with v49 with same error). Anyone else having the same issue with Unity 2022.2? Will try an earlier version of Unity but can't find out which Unity versions that uses Android SDK 29 or 30.
My App's OBB file is not being installed properly. This issue comes out of the blue...
I've never had an issue before the most recent Quest updates. Uploading new build .apk with .obb file sizes over 4.4gb total. When I try to get passed the first scene, the game's next scene will not load. This has never been an issue before and no lines of code have been changed. I was able to catch one of my fresh installs not properly installing. After I exited the game, the update button suddenly appeared even though it had already fully downloaded and installed the proper version number. This issue was confirmed by several players. I don't know what to do here. None of my new builds are allowing me to go passed the Main Menu even though it works flawlessly on PCVR. I suspect it has something to do with the .obb file not properly installing. I am in desparate need of help.
Applications just dissapear
Today I turned on the quest 2 and all the apps that I uploaded to AppLab on beta disapear. The ones that were installed just move to unknown apps but I cant access to the other ones. I search for them on the store but once they show and I click on them, and they dissapear. Is the verification something to do with that? It seems the need of a verification will be on Aug 16 so... dont know what is happening.
Unable to edit approved metadata to resolve review issues - Supported Controller / Player Modes
We received a response on our 10th Feb re-submission (v3) - there was an issue in the metadata selected I missed checking a couple of fields and we continued with the last selected settings 2 fields need changes: Supported Controllers: remove Hand Tracking Supported Player Modes: Remove Sitting and Standing, and select RoomscaleI tried to change these but am receiving this message - that is preventing me from saving the changes and resubmitting This metadata has been approved and cannot be modified. Go to the Submission Tab to create new metadata. There is no button to add new metadata on the Submission Tab. Not sure if this is a gap in the submission process or am I missing something? Q1. How do we edit our app metadata once it has been approved? We tried to change the build to an older one (1.04) to see if that would allow us to change the metadata. However, now we are unable to return to review the latest build submitted 1.05. We receive a message saying only draft builds can be attached to a submission. Q2. How can we return to the review of 1.05?Privacy policy issue when publishing the app to app lab
Hi everyone~ I am running into a privacy policy issue when we try to publish the app to the app lab. We didn't collect any user data in any form for our app, so we show that on our privacy policy page. But still, we receive feedback from the review team indicating we have some issues with our privacy policy. Here are 2 feedback from oculus team: I have 2 questions: 1 I have an assumption of the issue, which is our client wants to show, that in the future version, we will collect user data, but in the current version, we don't. Is this causing the misunderstanding? 2 If we show that we didn't collect any user data, do we still have to have a clear explanation of how the user may request all their data? If anyone has any idea or experience, please leave your thought, thank you so much.
