cancel
Showing results for 
Search instead for 
Did you mean: 

Change AndroidManifest.xml for AppLab submission.

AISDev
Honored Guest

I'm trying to get my app to be submitted into the AppLab, but I'm running into issues where no matter what I try, I always get those permissions active in my build:

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
android.permission.READ_MEDIA_VISUAL_USER_SELECTED

My app currently does not use any of those permissions, but I am currently using Oculus Interaction SDK (The old integration), so I have two options, to delete all the code that is tied to those permissions, or use another straighter (to the point) solution like modifying the manifest directly, I tried the following code using custom AndroidManifest.xml file checked on Player Settings:

<?xml version="1.0" encoding="utf-8" standalone="no"?>

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.CompanyName.MyApp"
xmlns:tools="http://schemas.android.com/tools">
<uses-permission android:name="android.permission.RECORD_AUDIO" tools:node="remove" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" 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" />
<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" />
</intent-filter>
</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.vr.focusaware" android:value="true"/>
</application>
<uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" />
</manifest>

 

 

 

But it simply did not work, not matter what I tried. 

I also tried building directly on Android Studio, but it did not work either. I don't know why the custom manifest is not working, well, actually it works but specifically the record audio part.

 

<uses-permission android:name="android.permission.RECORD_AUDIO" tools:node="remove" />

The other permissions simply stay there. I hope that maybe some good developer can help me with this issue.

Unity version: 2021.3.30f1, Using this packages:
AISDev_0-1707202410608.png

Thank you very much for your patience 😊



3 REPLIES 3

Big_Flex
Meta Employee

Hi @AISDev, that sounds frustrating! Thanks for posting here with that information. I've passed your question to the Interaction SDK team, and I or someone else will post here once we have a solution for you. 

Hello, thank you very much.
I went further and tried to see the permissions from the APK using aapt android tool and this is what it detected, that means that the permissions never were there in the first place and for some reason the APK Permissions tool Meta is using is detecting the wrong permissions or maybe I am not seeing the full picture of the issue. 

AISDev_1-1708131648649.png

Thank you for your response.

 

Were you able to fix this issue? I'm running into the same problem.