[iOS] Keyboard covers the entry
See original GitHub issueDeveloper Notes
-
AFAICT the sample attached to this issue wouldn’t have worked in XF either. In XF the entries would only scroll into view if you nested your content inside a ScrollView or a ListView
-
in XF ListView would scroll into focus but CollectionView would not
Approaches here
-
Follow the XF approach where it would set the ContentInsets on the UIScrollView in order to adjust the visible area
- This approach is a bit limited feeling though it’s been working on XF so possibly the best approach plus it’s in the docs here
-
Researching around I don’t see a lot of solutions natively that take the approach of scrolling the scrollview. They typically seem to use a layout guide on the root element and then set the height on that layout when the keyboard opens. I’ve also seen the approach of using Y translation.
- These two approaches technically match the “AutoResize” and “AutoPan” options we have on android so we could take both of these approaches and make these options apply more xplat opposed to platform specific
Description
The keyboard covers the entry in iOS. Whereas Entry should be above the Keyboard BugSample.zip
Steps to Reproduce
Run the repro project. Try to enter something in the Entry.
Version with bug
Preview 13 (current)
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 15
Did you find any workaround?
Workaround 1
https://github.com/PureWeen/ShanedlerSamples https://www.nuget.org/packages/PureWeen.Maui.FixesAndWorkarounds
builder.ConfigureKeyboardAutoScroll();
Workaround 2
https://github.com/drasticactions/Drastic.IQKeyboardManager
Relevant log output
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:78 (9 by maintainers)
Top Related StackOverflow Question
This problem is very serious. I don’t know which version can be repaired in the future, I hope the development team can pay attention to it.
I noticed that you postponed this issue to Iteration 4 (Feb - Mar).
I can’t understand why it doesn’t have maximum priority, as it makes it impossible to develop an iOS app with a simple entry without being afraid of it being covered by the keyboard. I honestly wouldn’t like to use a workaround for a such basic feature.
I can see you’re now working on https://github.com/dotnet/maui/issues/11702, which imo is something that could wait or, at least, not relevant as this issue.
I really appreciate all your hard work and I can understand it’s not easy to handle a project of this size, but these are the kinds of problem that drive away new and old developers. I think you’re losing an entire “generation” of new mobile developers and that’s a real shame because imo MAUI has the potential to become a leader in this field, checking what it can provide. I really hope MAUI will become what it’s supposed to be, but it’s more difficult to be confident when I see that major issues keep being postponed.