Search Issue Tracker
Won't Fix
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.
Comments (1)
-
NathanMitchel
Apr 06, 2023 16:04
The country's movement strategy is directed by the Law of Return that awards outsiders citizenship on the off chance that they have Jewish family members. Thus, there's almost no selectivity in who gets inside the country. Instead of Canada's credit-based migration strategy, Israel doesn't empower gifted individuals with no Jewish blood to coordinate into the country. That is the reason business supervisors need to know how to track down distant trained professionals.
Source: https://mobilunity.com/blog/hire-developers-in-israel/
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
- UI Builder can't set a background image to a sprite from a multi-sprite spritesheet in the Resources folder
- Light2D freeform does not render the internal part when rendered in certain shapes
- Using AddCopyPass causes an incorrect merging of passes.
- Negative Enum value is not pasted correctly when copying from another array
- Silent Crash when generating Lightmap UVs for a model with a large object scale
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.