Get Keyboard height incorrect
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- swift
- Domain
- mobile-dev
Research direction
Start by reproducing the issue with the IQKeyboardManager and IQKeyboardToolbarManager settings, the keyboardWillShowNotification observer, and a third-party keyboard on Xcode 16.4. Compare the first-launch keyboard height and notification count with IQKeyboardManager enabled and disabled. Done means the first keyboard presentation reports the correct height without the extra incorrect notification.
Written by the indexing model from the issue text.
Description
Describe the bug：
The app gets an incorrect keyboard height on the first use of the keyboard each time it launches, especially when a third-party keyboard is used as the default keyboard.
To Reproduce
Steps to reproduce the behavior:
IQKeyboardManager.shared.isEnabled = true
IQKeyboardToolbarManager.shared.isEnabled = true
NotificationCenter.default.addObserver(self,
selector: #selector(keyBoardWillShow(_:)),
name: UIResponder.keyboardWillShowNotification,
object: nil)
Expected behavior：
keyBoardWillShow Called 2 times, the keyboard height obtained via keyboardFrameEndUserInfoKey is incorrect.
Setting IQKeyboardManager.shared.isEnabled = false will make everything work normally.
Versions
Xcode: 16.4
Library Version: 8.0.1
- Dominant language
- Swift
- Stars
- 16.6k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 hackiftekhar/IQKeyboardManager
-
Xcode 27 UpdateOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hackiftekhar/IQKeyboardManager#2184 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
hackiftekhar/IQKeyboardManager#2182 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hackiftekhar/IQKeyboardManager#2181 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
hackiftekhar/IQKeyboardManager#2180 · 1 comment ·
-
UI OptimizationOpen
Difficulty 4/5 3-5 days Newbie friendliness 38/100
hackiftekhar/IQKeyboardManager#2178 · 1 comment ·
All issues in hackiftekhar/IQKeyboardManager
Similar issues
-
Native HTTP policy fixture rejects its pathless response URLPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug fixed (pending release)
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
vorssaint/vorssaint-utils#2810 · 1 comment ·
Maintainers usually reply within 1 day
-
Notion AI: getSpaces response exceeds 5 MB plugin limit for multi-workspace accountsPossibly taken A pull request linked to this issue is open or already merged. Openclawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:auth-provider issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
steipete/CodexBar#4341 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kiosk_set_screensaver_mode ignored: mode is not passed through by the notification parserPossibly taken @bgoncal claimed this today. Openbug ios
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/iOS#6001 ·
Maintainers usually reply within 1 day