Floating keyboard on iPadOS 15.1 leads to UI error

[xto3]

Platform and app information

iPadOS 15.1
Joplin App 12.4.2

Most of the time, I use the floating keyboard on my iPad:
https://support.apple.com/en-us/HT210758

Sequence

• When you edit a note on iPad with that floating keyboard
• Another window comes across after a few seconds and covers almost all the editing screen
• As a result, you cannot edit the note anymore
• It’s not strictly speaking a crash but in the end you get stuck and you need to force the app to close to make it usable again

Expected behavior

The open note in Joplin should remain editable with the floating keyboard as it does with the standard keyboard.

Screencast

RPReplay_Final1629723233.mov

[grem11n]

Facing the same bug with:

• iPad OS 14.7.1 (18G82)
• Joplin 12.4.2

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[xto3]

Hi!

The last version of Joplin doesn’t seem to address the issue.

Is there any plan to address it in the future?

Thanks again for the good job with Joplin!

[grem11n]

Although, it looks like a duplicate for:

• iOS app, iOS 14, bottom layer go to top after add new notebook or edit. #3768
• iOS - UI Glitch - White Screen Blocks Text #4980

Looks like #4980 has the most activity in it. However, this issue is not addressed yet. Moreover, according the the input from those two issues, it affects not only iPadOS, but iOS as well.

[xto3]

Thanks for your reply!

Indeed, I hadn't see those issues prior to post. I will have a look on #4980.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.