Search Issue Tracker
Fixed
Fixed in 4.4.0
Votes
0
Found in [Package]
4.3.0
Issue ID
OXPB-160
Regression
No
Bluetooth permission is removed from the AndroidManifest.xml when the Oculus XR Plugin is installed and the Player is built
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the Build Settings Window (File > Build Settings)
3. In the Build Settings Window, press the “Build” button
4. Open the built APK with Android Studio APK Analyzer
5. Observe the AndroidManifest.xml file
Expected result: The Android Manifest contains “Bluetooth” permission
Actual result: The Android Manifest does not contain “Bluetooth” permission
Reproducible with: 3.4.1 (2021.3.44f1), 4.3.0 (2022.3.49f1, 6000.0.22f1)
Reproducible on: MacOS 14.6.1 (Intel), Windows 10 (user’s)
Not reproducible on: No other environment tested
Note: The issue occurs regardless of whether the ‘tools:node="remove"’ is added to the AndroidManifest.xml prior to the build process
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 4.4.0):
Changed build process to keep Bluetooth permissions tag added to the manifest.