I also wrote up how I got around the AndroidManifest Unity bug by editing the manifest file if it helps anyone:
https://www.stornaway.io/tech-tip-when-meta-quest-developer-hub-objects-to-android-permission-read_phone_state/
It is crazy that this is still a thing.
For search: The error reported by Meta Quest Developer Hub says:
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.
It also contains the following complaint for permissions currently added by Unity despite using a custom manifest:
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
These are not blocked up front in the same way as READ_PHONE_STATE above, but with a standard app you will need to remove these before submitting to the store in order for your app to be accepted.
