Thanks for submitting this! We will try to get it in the next release

_{Sent with GitHawk}

@davidvpe Thanks for your fix, can you add a CHANGELOG entry in the CHANGELOG.md?

@zhongwuzw Changelog added!

I need to test this before merging to make sure it doesn't mess up my company's app

@davidvpe I took a moment to test this out with the new example app I'm making an it looks like its still not sizing the bottom correctly

Its added more spacing than needed, see below

It works on iPhone/iPhone+ models so I believe the issue is that you are not deducting the iPhoneXBottomInset

I think it's the iPhoneX.

I tried this on an iPhone X and is working just fine,

@davidvpe How are you setting up the container controller?

@davidvpe as a safety measure, can you add an additionalBottomContentInset: CGFloat = 0 in MessagesViewController and when you calculate the new bottom inset add it.

_{Sent with GitHawk}

@nathantannar4 maybe we should add additionalTopInset as well? we had these in an earlier version of MessageKit, I forgot the reason why I removed them 🤔

@nathantannar4 I am a bit caught up at work but as soon as I get some free time I'll add it.

@SD10 agreed we should have the additional top inset as well,

Thanks @davidvpe !

@nathantannar4 I see there is a messageCollectionViewBottomInset in MessagesViewController maybe I should just add it to the equation and that's it.

Edit: Turns out it is being subtracted already from the equation. Huh

Yeah we really need to do a thorough analysis of what's going on here. It's such a struggle to get the inset working for everyone. We make changes for one app / device and break things in another

We should definitely expose some additionalBottomContentInset and additionalTopContentInset properties for people to fix things if they need to.

@davidvpe messageCollectionViewBottomInset is a convenience property that sets the bottom inset of the view and scroll indicator. It does not allow users to add additional inset.

@SD10 I think this is better than what we currently have. I can do a separate PR for adding additional top/bottom inset so devs can adjust those as needed and we shouldn't have to handle more of these issues.

_{Sent with GitHawk}

Yeah @nathantannar4 it's just pending me testing this change in our application. I have a tight deadline at work right now so I won't get to it till this weekend. We use Carthage as a dependency manager -- so testing MessageKit changes is a little inconvenient for me with this setup

Hey @davidvpe, we really appreciate you getting the ball rolling on this PR 👍. However, it looks like #787 is becoming a better fit for MessageKit. I've just sent you an invite to the MessageKit organization. Thanks again 💯