Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.40f1
2021.3.13f1
2022.2.0b12
2023.1.0a13
Issue ID
UUM-20746
Regression
No
[Android] 2D Mobile Template issues: Project Version, Bundle Identifier, Full Logging Default Settings are wrong when creating a new project
Reproduction steps:
1. Create a new 2D Mobile Template project through Unity Hub and open it
2. Open File > Build settings > Player Settings > Player > Android settings
Expected result: Project Version is 0.1, Bundle identifier is using the project’s name, Logging level matches non-mobile specific templates (2d, 3d)
Actual result: Project Version is 1.0.2, Bundle identifier is using the template name, Full Logging is on
Reproducible with: 2020.3.40f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b12, 2023.1.0a13
Reproducible on: MacOS 12.4 (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
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
- "Debug Draw Mode" unchecked checkboxes are not visible
- [Android] App crashes when Volume Depth of Field is set to "Bokeh" while using Vulkan Graphics API
- Baked Off Mesh Links outside the modified area are deleted when using NavMeshSurface.UpdateNavMesh
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.
Resolution Note (2023.1.X):
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.