Search Issue Tracker
Fixed
Votes
6
Found in
2022.2.7f1
2023.1.0b4
2023.2.0a2
Issue ID
UUM-27136
Regression
Yes
[Android] installLocation in AndroidManifest.xml is set to preferExternal whilst in Player Settings other value was set
How to reproduce:
1. Open a new Unity project
2. Set “Install Location” to anything besides “Prefer External” in the Player Settings
3. Toggle on the “Export Project” flag in the Build Settings
4. Export the project
5. Observe the contents of “AndroidManifest.xml” file located under the exported project
Expected result: android:installLocation is the equivalent value set in the Player Settings
Actual result: android:installLocation="preferExternal" is set in the file
Reproducible with: 2022.2.0a16, 2022.2.7f1, 2023.1.0b4, 2023.2.0a2
Not reproducible with: 2021.3.18f1, 2022.2.0a15
Couldn’t test with: 2020.3.45f1 (no InstallLocation field in the Player Settings)
Reproduced on: macOS 13.0 (Intel)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-25965