To get rid of the wonky behavior, I removed the keyboard observer and added a delegate to textview. This additionally gives me more control over what the user is doing with the textview. I have been working on an application for my dojo in Japan for about five months now. Created a short video with the auto-scroll and textview animation I have for the comment section. https://drive.google.com/file/d/1nBd18heWpoA0HYBK1O4uhNmwOe1UOC9K/view func textViewDidBeginEditing(_ textView: UITextView) { scrollToLastItem() } fileprivate func scrollToLastItem() { self.collectionView.scrollToItem(at: [0, items.count - 1], at: .bottom, animated: true) }

Hi Brian I try the code override becomefirstresponder and inputaccessoryview but the redview doesnt show up at all

Hey Brian! Why don't we use an UITextField instead of a UITextView? As it already has .placeholder property? Thanks!

Hey Brian, When I go to dismiss my keyboard I am getting this error message below, It doesn't cause my app to crash but it is causing some glitchy behavior in my collection view - [View] First responder warning: '<UITextView: 0x7f869b859000; frame = (10 0; 354 40); text = 'Message...'; clipsToBounds = YES; gestureRecognizers = <NSArray: 0x6000012d90b0>; layer = <CALayer: 0x600001cc21e0>; contentOffset: {0, 0}; contentSize: {354, 28}; adjustedContentInset: {0, 0, 0, 0}>' rejected resignFirstResponder when being removed from hierarchy Thanks for any help!

Hi Brian, is "textView.insertTextPlaceholder(with: <#T##CGSize#>)" a workaround with Swift5 to the the 'placeHolderLabel' used in this session? Thanks a bunch.

When I click on the inputAccessoryView, it stretches becoming half of the view.frame.width, I don't know why

Great episode. Thank ya ?