FYI - still getting this in 2019.3.b1
Just found out you can add an empty adb1.txt next to your Assets folder to force it to use the old Asset Database, which is a usable workaround for now.
FYI - still getting this in 2019.3.b1
Just found out you can add an empty adb1.txt next to your Assets folder to force it to use the old Asset Database, which is a usable workaround for now.