Skip to content

Conversation

Kdmeenaa
Copy link

Fix issue: #2112
/claim #2112

@Kdmeenaa
Copy link
Author

Kdmeenaa commented Jul 1, 2025

Hi @hackiftekhar, kindly review this PR whenever you get time. It resolves issue #2112. Thank you! 🙌

@hackiftekhar
Copy link
Owner

Hi @Kdmeenaa I reviewed the project and I would like to ask that this fix was done in the demo project. What's the change in the actual library?

@Kdmeenaa
Copy link
Author

Kdmeenaa commented Jul 5, 2025

Hi @hackiftekhar 👋
Thanks for pointing this out.

You're right — currently the fix is implemented only inside the demo project (ExampleTableViewController.swift) for testing and reproducing the issue in a controlled environment.

Here's what I did so far:

  • Used the demo to simulate the keyboard inset issue with UITableView.
  • Verified that applying the fix in the demo resolves the problem.

What I’ll do next:

I'll move the relevant logic into the actual IQKeyboardManager library (likely in IQKeyboardManager.swift) so that it benefits all users of the library — not just the demo.

Will push an updated commit shortly. 👍

Thanks for the feedback!

override func viewDidLayoutSubviews() {
super.viewDidLayoutSubviews()

if let tableView = self.view.subviews.first(where: { $0 is UITableView }) as? UITableView {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please create an @IBOutlet reference of UITableView from storyboard and then use it directly instead of finding it in subview.

Copy link
Owner

@hackiftekhar hackiftekhar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a comment for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants