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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
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.