@Frameworks Engineer Thank you for your reply. I highly encourage you to read my updated question on stack overflow. In particular, the question has been made explicit and is also clearly introduced by a header (it's too long to fit here). Could you answer the question by modifying the provided code? Playing around with configurationUpdateHandler didn't do it.

Thank you, however it doesn't make much sense that the button's action is triggered without any animation to indicate that.

[2/2] In particular, your solution does not take into account the fact that the keyboard frame might change, the fact that the text view might have input accessory views, that the view controller might be embedded in a collection view controller, that the app scene might be floating on an iPad or that there have been changes in the timing with which the keyboard is shown in iOS 17 with respect to earlier iOS versions. All of these cases and more are handled by the up to date API.

[1/2] I see, but it looks like this approach is no longer recommended: I can't find "The Keys to a Better Text Input Experience", the WWDC session that is mentioned in "Your guide to keyboard layout". Considering that it is impossible that Apple does not explain you how to comprehensively (as explained in my next reply due to constraints) handle the keyboard being laid out if your app uses a collection view controller and that I can't find such documentation, do you happen to have a link to it?

Thank you, could you please give a look at this question?

@Frameworks Engineer Thank you very much. You also need to set the text view's isScrollEnabled property to false.