[WIP] An unexpected extra bottom edge inset appears in the UITableView when the keyboard is presented.

[Copilot]

• Explore repository structure and understand the IQKeyboardManager codebase
• Identify the issue location in content inset adjustment logic
• Located the problematic code in both Swift and Objective-C versions in adjustScrollViewContentInset function
• Analyze the root cause of the extra bottom edge inset calculation
• Create a minimal fix for the double safe area inset subtraction
• Test the fix with demo applications
• Verify the fix works correctly in both Swift and Objective-C versions

The issue appears to be in the content inset calculation where safeAreaInsets.bottom is being subtracted from bottomInset, potentially causing an unexpected extra bottom edge inset in UITableView when the keyboard is presented.

Location of the issue:

• Swift: IQKeyboardManagerSwift/IQKeyboardManager/IQKeyboardManager+Position.swift line 623
• Objective-C: IQKeyboardManager/IQKeyboardManager.m line 1123

Fixes #2112.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.