Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.39f1
2021.3.10f1
2022.1.15f1
2022.2.0b8
2023.1.0a10
Issue ID
UUM-15083
Regression
No
Bundle Identifier showing wrong value when creating a Project with 2D Mobile Template
Reproduction steps:
- Open Unity Hub
- Create a New Project
- In the Template selection screen select 2D Mobile
- Open the Project
- Go to Edit > Project Settings > Player > Android settings
- Under Identification observe “Package Name”
Expected result: com.DefaultCompany.ProjectName
Actual result: com.DefaultCompany.com.unity.template.mobile2D
Reproducible with: 2020.3.39f1, 2021.3.10f1, 2022.1.15f1, 2022.2.0b8, 2023.1.0a10
Reproducible on: MacOS 12.4 (Intel)
Note: The Expected result would change depending on the Company name and Project name upon creation.
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
- Localization Group Rules bypasses Locale logic when SharedGroup asset provided
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
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.