I am unable to upload to the production channel due to my Andriod manifest.
I am working on a MR application. Whenever I attempt to upload to the production channel I get this error: This APK includes the feature, `com.oculus.experimental.enabled`, which is not allowed. Please remove it from AndroidManifest.xml and retry. I have removed the line "<uses-feature android:name="com.oculus.experimental.enabled" android:required="true" />" from the manifest, yet the issue persists. Here is my entire manifest: <?xml version="1.0" encoding="utf-8" standalone="no"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" android:installLocation="auto"> <application android:label="@string/app_name" android:icon="@mipmap/app_icon" android:allowBackup="false"> <activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:configChanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:launchMode="singleTask" android:name="com.unity3d.player.UnityPlayerActivity" android:excludeFromRecents="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> <category android:name="com.oculus.intent.category.VR" /> </intent-filter> <meta-data android:name="com.oculus.vr.focusaware" android:value="true" /> </activity> <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" /> <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only" /> <meta-data android:name="com.oculus.ossplash.background" android:value="passthrough-contextual" /> <meta-data android:name="com.oculus.telemetry.project_guid" android:value="76f99eb0-5638-4124-901c-3b3917cb882b" /> <meta-data android:name="com.oculus.supportedDevices" android:value="quest2|questpro|eureka" tools:replace="android:value" /> </application> <uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" /> <uses-permission android:name="com.oculus.permission.USE_ANCHOR_API" /> <!-- <uses-feature android:name="com.oculus.experimental.enabled" android:required="true" /> --> <uses-feature android:name="com.oculus.feature.PASSTHROUGH" android:required="true" /> <uses-permission android:name="com.oculus.permission.USE_SCENE" /> <uses-permission android:name="android.permission.READ_PHONE_STATE" tools:node="remove"/> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" tools:node="remove"/> <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" tools:node="remove"/> <uses-permission android:name="android.permission.READ_MEDIA_AUDIO" tools:node="remove"/> <uses-permission android:name="android.permission.READ_MEDIA_VIDEO" tools:node="remove"/> <uses-permission android:name="android.permission.READ_MEDIA_IMAGES" tools:node="remove"/> <uses-permission android:name="android.permission.ACCESS_MEDIA_LOCATION" tools:node="remove"/> <uses-permission android:name="android.permission.READ_MEDIA_IMAGE" tools:node="remove"/> </manifest>
How do any of you upload to applab with the AndroidManifest issue?
It seems that no matter what I do AppLab is saying that the APK AndroidManifest contains unapproved permission, but it doesn't. Those permission are specifically disabled in the manifest. I have tried upload over a dozen times now trying various things. I have seen this question asked a lot without any kind solid resolution. I am using Unity and developing for Quest 3. Is there not some kind of standard and time tested solution to this issue? Thank you.
how to enable ACCESS_FINE_LOCATION on my app
Hi, I have an app that connects to a BLE Speed Sensor, but in order to do so I need to have "android.permission.ACCESS_FINE_LOCATION" enabled. In my previous build I had it declared in my AndroidManifest.xml and was able to publish it without trouble but now the Oculus Developer Dashboard won't let me add this permission this way anymore. The alternative seems to be using Unity's Permission.RequestUserPermission(Permission.FineLocation); but this doesn't pop up any permission requests and therefore my app throws an error stating that it does not have the aforementioned permission. Is there a workaround? I've searched the internet but the only solution mentioned was downgrading the Oculus XR Plugin version, which does not seem to be an option anymore for this scenario.
There is no "Create store-compatible AndroidManifest.xml" menu
I have an app ready for upload to the oculus store for Oculus Go. development version builds and runs great on device. My app is not accepted when uploading to the store beta channel with some basic errors which should be easy to resolve. the official oculus documentation says: "To generate the Oculus store-compatible Android manifest file, in the menu, go to Oculus > Tools > Create store-compatible AndroidManifest.xml." ( developer dot oculus dot com / documentation/unity/unity-conf-settings/) However I do not have this menu option: using Unity 2019.3.10f1 with the following oculus integration: The values in the android manifest i need to change are simple, as shown in the oculus store when I attempt to upload the APK: HOW CAN I EDIT THE MANIFEST APPROPRIATELY????
Removing manifest permissions
Hello! I have issues with the following manifest permissions, which I don't need or use in my app: android.permission.RECORD_AUDIO android.hardware.microphone android.permission.READ_EXTERNAL_STORAGE I've overcome this by selecting skip permissions = true; This solves the issue but created a new one. I need the ACCESS_FINE_LOCATION which became also unavailable because of skip permissions. What can be done to properly set the manifest with the right permissions? Thanks!
Android Manifest created by Oculus and Unity adds unwanted "android.permission.READ_PHONE_STATE"
Hello -- I am building an app using Unity. When I build it the following line is added to the Android Manifest <uses-permission android:name="android.permission.READ_PHONE_STATE" /> According to android documentation, this is added automatically if one of the manifests does not specify a minimum sdk with api >4. There is an AndroidManifest that appears after building in the temp\stagingarea\android-libraries\ovrplugin -- it does not have this specified so I suspect that what ever is generating this file is the culprit in causing the unwanted line in the primary AndroidManifest. My question is: What in OVR is creating this manifest (temp\stagingarea\android-libraries\ovrplugin\AndroidManifest) and how do I go about changing it so that when it is generated it adds the proper minimum sdk information. Note1: This happens with a project with almost nothing in it. Clicking VR Oculus in player settings does it. Note 2: one of the "fixes" is to add another permissions line with tools to remove, however, this solution is not one that will work for me due to google play requirements.
