scrollToLastItem(at:animated:) is not scrolling to bottom properly.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the issue in the Example app's Basic Example screen, then trace the scrollToLastItem(at:animated:) entry point and its handling of the collection view's bottom inset. Compare programmatic scrolling with manual scrolling. Done means the gap between the last message cell and inputBarAccessoryView remains after automatic scrolling.
Written by the indexing model from the issue text.
Description
The Bug
The scrollToLastItem(at:animated:) method is not scrolling to the bottom properly. It eliminates the gap between last cell and inputBarAccessoryView. This issue is visible in the video I recorded from the Example app of MessageKit. It seems the method only makes the last item completely visible without considering the bottom inset and eliminates the space between the inputBarAccessoryView and the message cell.
To Reproduce
Open Example MessageKit app, open Basic Example screen, wait for bots to send message, or you can send yourself, messagesCollectionView will scroll to bottom automatically. Then try to scroll manually, it will scroll a little bit more, which is expected when programatically scrolled.
Expected behavior
The gap between inputBarAccessoryView messagesCollectionView should be kept when programatically scrolled.
Screenshots
Environment
-
What version of MessageKit are you using?
4.2.0 (commit c7f278c) -
What version of iOS are you running on?
IOS 17.0.1 on Simulator iPhone 15 Pro Max
IOS 17.2.1 on Physical Device iPhone 13 -
What version of Swift are you running on?
Swift 5.9 -
What device(s) are you testing on? Are these simulators?
IOS 17.0.1 on Simulator iPhone 15 Pro Max
IOS 17.2.1 on Physical Device iPhone 13 -
Is the issue you're experiencing reproducible in the example app?
Yes.
(I don't know why but GIF is not repeating, you can see it after refresh)
- Dominant language
- Swift
- Stars
- 6.3k
- Forks
- 1.2k
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MessageKit/MessageKit
-
Keyboard bug Openbug?
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MessageKit/MessageKit#1901 ·
-
question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MessageKit/MessageKit#1888 · 2 comments ·
-
Transparent navigation bar in messageInputBar but messagesCollectionView is not shown in these areas Openfeature request
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MessageKit/MessageKit#1884 · 1 comment ·
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MessageKit/MessageKit#1880 ·
-
bug?
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MessageKit/MessageKit#1878 ·
All issues in MessageKit/MessageKit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area:general bug P1 security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
uttrflow/uttrflow-swift#1333 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
maxgoedjen/secretive#840 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
manaflow-ai/cmux#13763 ·