Virtual Keyboard overlaps typing area on iPhone XR

[JamesE]

Result: When typing in a document, the virtual keyboard overlaps most of the current line of text so the user cannot see what they are typing.
Expected Result: To be able to see the text being written on the screen above the virtual keyboard.

1. Open Scrivener iOS on iPhone XR
2. Go into a project.
3. Open a new document or an existing one.
4. Type down to line 21 or lower.
5. Observe the text as it prints to screen is beneath the virtual keyboard.

This occurs regardless of which keyboard features are enabled. It also occurs on third party keyboards if enabled. It will occur if adjusting line spacing on Scrivener as well.
Tested on iOS 13.2.3, iPhone XR, Scrivener for iOS version 1.2.
Repeatability 3/3

The attached image displays the issue.

[AmberV]

Firstly, try upgrading to Scrivener 1.2.1, as tweaks were made to the scrolling of text around the keyboard.

[Monkeyboy]

I’m having the same problem, have been for a while now and it makes the app unusable. I’m on an iPhone SE. Updating to 1.2.1 doesn’t fix the issue.

[JimRac]

Yup, I’m seeing this too, on an iPhone 7 running 12.4.1. Using Scriv 1.2.1.

[Monkeyboy]

I think I’ve found a fix. Delete Scrivener from your phone and reinstall it. I also rebooted the phone before downloading it again from the App Store. The last line of text now doesn’t disappear below the keyboard! No guarantees this’ll work for other users but it worked for me! Wish I’d tried this sooner.

[JimRac]

I think I’ve found a fix. Delete Scrivener from your phone and reinstall it. I also rebooted the phone before downloading it again from the App Store. The last line of text now doesn’t disappear below the keyboard! No guarantees this’ll work for other users but it worked for me! Wish I’d tried this sooner.

Unfortunately, delete/reboot/reinstall didn't work for me.

ETA: I've submitted a ticket to L&L support.

[Monkeyboy]

I think I’ve found a fix. Delete Scrivener from your phone and reinstall it. I also rebooted the phone before downloading it again from the App Store. The last line of text now doesn’t disappear below the keyboard! No guarantees this’ll work for other users but it worked for me! Wish I’d tried this sooner.

Unfortunately, delete/reboot/reinstall didn't work for me.

ETA: I've submitted a ticket to L&L support.

I spoke too soon. The text is disappearing below the keyboard again. Very frustrating. Such a small thing ruins the app.

[AmberV]

Thanks for the updates, we've got it on the list to look into tweaking it further.

Meanwhile this should be relatively simple to work around, no? Just leave some empty lines at the end of the file. I can't reproduce this myself, so I don't know if it works, but it seems logical to me.

[JimRac]

Yes, Iowa, I just did a quick test, and leaving a few blank lines at the end of the doc seems to be a viable work around.

[Monkeyboy]

The blank lines thing doesn’t seem to work for me. You end up at a point where after five or six lines of typing it still drops below the keyboard.

[AmberV]

Are you typing above the empty lines? The idea is to basically simulate typewriter scrolling, which does something very similar to that.

[Monkeyboy]

Yes, I’m typing above the empty lines.

[AmberV]

How much text would you estimate you need to write, and is this something where you see the scroll point gradually getting worse and worse, into the empty lines you added? I’ve never seen anything remotely that bad on my own device, which is why I have to ask. Sometimes the very edges of descenders crop into the keyboard a bit, but that’s the most I’ve ever seen—certainly not whole paragraphs.

[katlovergilpin]

I am having this issue as well. The scroll is not working on my iPhone 11. It doesn’t matter how many lines I enter, I eventually catch up and everything is hidden by the keyboard. When I do scroll up, my blank lines are still there, but the app no longer follows along. I suppose that’s a good way of putting it.

[Lewis-H]

I’m having this issue. Weirdly I’ve found that switching to the emoji keyboard and then back to the regular keyboard fixes it. Needs a proper fix still but that’s a good workaround. I have reported this issue to the Apple support team hopefully they solve this issue soon.