Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.24f1
2021.2
2022.1
2022.2
Issue ID
1407760
Regression
No
Custom Gradle path in Android External Tools only respects the last closed Editor instance
Reproduction steps:
1. Create two new projects on two different Unity versions
2. Navigate to Preferences > External Tools in both projects
3. In Gradle Installed with Unity section set a custom path for Gradle (e.g. you can point to a Gradle direction that was installed with that Unity version)
4. Close both Editors
5. Open the first closed project
6. Navigate to Preferences > External Tools and observe Gradle paths in Gradle Installed section
Expected result: Both Editor custom Gradle paths are relative to the project
Actual result: Both Editor custom Gradle paths are equal to the last closed project
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.14f1, 2022.1.0b11, 2022.2.0a7
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note:
It's an Editor setting, not project setting. It is the same for not only for all project, but also for all Editor versions (if you have more than one installed).