Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.19.19
1.21.20
2.0.8
Issue ID
ADDR-3635
Regression
No
[Android] Unnecessary "android.permission.INTERNET" permission is being added to the "AndroidManifest.xml" when using the Localization package due to Addressables package dependency
How to reproduce:
1. Create an empty project on an Android Platform
2. Open the Package Manager
3. Install the Localization package
4. In the Build Settings "Run Device" dropdown, select the desired device
5. Press Build
6. Open Android Studio
7. Open "Build/Analyze APK..." and choose built APK
8. Select the "AndroidManifest.xml" file
9. Search for "android.permission.INTERNET" in the "AndroidManifest.xml" file
Expected result: "android.permission.INTERNET" is not added to the "AndroidManifest.xml"
Actual result: "android.permission.INTERNET" is added to the "AndroidManifest.xml"
Reproducible with: 1.19.19 (2021.3.35f1), 1.21.20 (2022.3.20f1), 2.0.8 (2023.2.10f1, 2023.3.0b7)
Testing environment: Windows 10 Pro, Windows 11 (User reported)
Not reproducible on: No other environment tested
Note: also reproducible if the Addressables package is installed separately
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.