Does anyone know if they've fixed this issue yet?

Same. I find out a solution to avoid it by putting conditions outside like below, but this will lead no animations. .tabViewBottomAccessory { if A { ViewA() }else{ ViewB() } } I don't think they were really ready to release these new APIs...

you guys can find a workaround in here

withAnimation { offset = contentHeight isFocused = false // binding to textfield } completion: { isPresented = false } I just find out this line causes the case, maybe bacause the keyboard animation interupt this animation.