ClearAvatarData is called, as expected, which should clear the blueprint id, however HandleAvatarSwitch doesn't return, so it continues further down and winds up calling _visibilityPopup.value = null.

Since _visibilityPopup's formatter is selected => selected.Substring(0,1).ToUpper() + selected.Substring(1), this immediately throws an NPE and crashes the dialog until it's completely restarted.

hasRemoteAvatarRecord should probably be false in the cases when ClearAvatarData is called, rather than remaining true for these invalid flows.