Following this, I'm still having this issue with XCode 12.0 Beta 6. Is there any official response from Apple regarding this? If it's deemed as an expected behaviour in the future, we need to plan a big code update...