Search Issue Tracker
Fixed
Fixed in 2021.3.42f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5
Votes
0
Found in
2021.3.41f1
2022.2.6f1
2023.1.0b3
2023.2.0a3
Issue ID
UUM-27090
Regression
No
**DIR_UNITYPROJECT** is not resolved correctly in settingsTemplate.gradle
To reproduce:
* Open attached project
* Inspect Assets\Plugins\Android\mainTemplate.gradle and Assets\Plugins\Android\settingsTemplate.gradle and notice where **DIR_UNITYPROJECT** is located
* Export gradle project, inspect:
** settings.gradle -> **DIR_UNITYPROJECT** was resolved incorrectly into empty string
** unityLibrary\build.gradle -> **DIR_UNITYPROJECT** was resolved into project path as expected.
This bug will affect Google's ED4MU, since it will need to use **DIR_UNITYPROJECT* in settingsTemplate.gradle, thus it's important to have it fixed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Add comment