Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.1.X, 2017.2.X, 2017.3.X
Votes
7
Found in
2017.1.0f3
Issue ID
931944
Regression
Yes
AssetDatabase.GetSubFolders does not work at all since 2017.1
Repro: Run attached editor tests on 5.6 and 2017.1, note that:
1. The documentation is incorrect, it suggests that we accept absolute paths (not the case, in 5.6 or 2017.1)
2. The feature has stopped working at all since 2017.1
Regression introduced in - 2017.1.0a1
Reproducible with - 2017.2.0b3, 2017.1.0f3,
Not reproducible with - 5.6.2p4, 5.5.4p2
Fixed in: 2018.1.0a2, 2017.3.0b5, 2017.2.0p1, 2017.1.2p1
Comments (7)
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
AntonQvarfordt
Nov 16, 2017 19:30
Still not working for me with 2017.2.0f3
Jinl
Oct 26, 2017 19:01
not fixed in 2017.2.0f3 on Sierra platform. Using alternative System.IO method
hd-wooga
Oct 16, 2017 08:16
Fixed in 2017.1.2p1
Jaacob
Oct 15, 2017 14:11
Same in 5.6.2p3.
Tried project folder, Application.dataPath, absolute path, slashes and backslashes, empty path, all combined, didn't get any result whatsoever. Seems the method only returns string[0].
allenwp
Aug 22, 2017 21:26
Yep. Using System.IO.Directory.GetDirectories instead as a workaround for now...
hd-wooga
Aug 04, 2017 08:12
Same here in 2017.1.0p2
xdegtyarev
Jul 27, 2017 12:16
Has same issue, it always returns 0 subfolders in list