Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0f4
2020.1
2020.2
2020.2.0a10
Issue ID
1244305
Regression
No
External tool path slashes are inconsistent and does not represent MS-DOS standard
How to reproduce:
1. Open any project with android support
2. Navigate to Preferences > External Tools
3. Check the "Recommended" checkboxes
4. Observe the JDK/SDK/NDK paths
Expected Behaviour: All paths have the same slashes (Preferably "\" as it is MS-DOS standard)
Actual Behaviour: Path slashes are not the same (Observe SDK and JDK last slashes), also, the slashes do not represent MD-DOS standard
Reproducible with: 2019.3.13f1, 2020.1.0b9, 2020.2.0a10
Could not test on 2018.4 since it does not have the visible path when the checkbox is checked
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
Add comment