Search Issue Tracker

Fixed in 16.9.0

Votes

0

Found in

16.7.0

Issue ID

UUM-131310

Regression

No

Player for Meta Quest crashes when using Vivox package and using Custom Main Manifest

UGS Vivox

-

Reproduction steps:
1. Open the attached project “ReproProject“
2. Switch to the Android platform in Build Profiles (File → Build Profiles → Select Android, press “Switch Profile”)
3. Make sure that Custom Main Manifest“ option is enabled (located at Edit → Project Settings → Player → Publishing Settings, option “Custom Main Manifest“)
4. Include line “{{<uses-permission android:name="android.permission.READ_PHONE_STATE" tools:node="remove" />}}“ in the Custom Manifest located at “/Assets/Plugins/Android/AndroidManifest.xml”
5. Build the Player
6. Launch the Player on the device
7. Observe the crash

Reproducible in: 16.7.0 (6000.2.6f2)

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740

Workaround: Include line “{{<uses-sdk android:minSdkVersion="14" />}}“ in the Custom Main Manifest

Note: CQA was not able to reproduce the crash

  1. Resolution Note (fix version 16.9.0):

    The reporter of the issue in Unity Discussions was happy with the resolution: https://discussions.unity.com/t/apk-stopps-working-in-quest-vr-when-activating-manifest-becuase-i-need-ot-remove-read-phone-state/1697482/21

  2. Resolution Note:

    The reporter of the issue in Unity Discussions was happy with the resolution: https://discussions.unity.com/t/apk-stopps-working-in-quest-vr-when-activating-manifest-becuase-i-need-ot-remove-read-phone-state/1697482/21

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues