Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.17f1
2023.2.0b14
2023.3.0a10
Issue ID
UUM-55107
Regression
No
[Android] AddUsesPermission() allows multiple identical permissions when called twice
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Open the Build Settings window (File > Build Settings)
4. Click Export
5. Create and select “GradleBuild” folder
6. Open the AndroidManifest.xml (GradleBuild\unityLibrary\src\main\AndroidManifest.xml)
7. Search for the uses-permission elements named "lolkekcheburek"
Expected result: Only one uses-permission element named "lolkekcheburek" is present
Actual result: Two uses-permission elements are named “lolkekcheburek“
Reproducible with: 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Could not test with: 2021.3.31f1, 2022.3.11f1 (Assets\Scripts\Editor\ManifestExtensions.cs(2,28): error CS0234: The type or namespace name 'Manifest' does not exist in the namespace 'Unity.Android.Gradle')
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- The issue does not reproduce when using the AddUniqueUsesPermission()
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.