Mail App 5.5.6: Missing Virtual Keyboard / Cursor in Input Fields on Mobile Browsers

Nextinger · October 6, 2025, 11:11am

The Basics

Nextcloud Server version (e.g., 29.x.x):
- 31.0.8
Operating system and version (e.g., Ubuntu 24.04):
- Linux 6.8.12-8-pve x86_64
Web server and version (e.g, Apache 2.4.25):
- replace me
Reverse proxy and version _(e.g. nginx 1.27.2)
- replace me
PHP version (e.g, 8.3):
- 8.3.23
Is this the first time you’ve seen this error? (Yes / No):
- yes
When did this problem seem to first start?
- after updating mail app to 5.5.6
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- no

Summary of the issue you are facing:

On mobile devices (smartphones), it is impossible to compose emails using the Nextcloud Mail App because neither the cursor appears nor the virtual (on-screen) keyboard is displayed when tapping on any text field (Recipient, Subject, Body). Consequently, no text input is possible and one cannot write an email.

The issue occurs both in the standard mobile view and after activating the desktop mode in the browser.

Steps to Reproduce

Open the Nextcloud instance on a smartphone via a browser.
Go to the Mail App.
Click the button to compose a new email.
Attempt to type in the “To” (Recipient), “Subject”, or the Message Body field.

Expected Behavior

When tapping on a text field:

The text input cursor should appear in the field.
The native smartphone virtual keyboard should pop up.

Actual Behavior

Neither the cursor nor the virtual keyboard appears. Text input is impossible.

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

{
    "system": {
        "debug": false,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "trusted_domains": [
            "cloud.musikschulefuerth.de",
            "168.119.71.43"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "31.0.8.1",
        "overwrite.cli.url": "http:\/\/cloud.musikschulefuerth.de",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "default_language": "de",
        "default_phone_region": "DE",
        "default_locale": "de_DE",
        "mysql.utf8mb4": true,
        "memcache.local": "\\OC\\Memcache\\APCu",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpmode": "smtp",
        "mail_sendmailmode": "smtp",
        "mail_smtpauthtype": "LOGIN",
        "mail_smtpauth": 1,
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "465",
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "maintenance": false,
        "maintenance_window_start": 1,
        "theme": "",
        "loglevel": 1,
        "log_rotate_size": 104857600,
        "skeletondirectory": "\/home\/vir10TB\/data\/eigenes-skeleton",
        "app.mail.smtp.timeout": "60",
        "mail_smtptimeout": 30,
        "updater.release.channel": "stable",
        "app_install_overwrite": [
            "documentserver_community",
            "snowflakestheme",
            "occweb"
        ],
        "mail_smtpsecure": "ssl",
        "memories.exiftool": "\/var\/www\/nextcloud\/apps\/memories\/exiftool-bin\/exiftool-amd64-glibc",
        "memories.vod.path": "\/var\/www\/nextcloud\/apps\/memories\/exiftool-bin\/go-vod-amd64",
        "dav": {
            "sync_chunk_size": 10000
        }
    }
}PASTE HERE

Apps

Enabled:

app_api: 5.0.2
bruteforcesettings: 4.0.0
calendar: 5.5.5
calendar_resource_management: 0.10.0
circles: 31.0.0
cloud_federation_api: 1.14.0
comments: 1.21.0
contacts: 7.3.2
dashboard: 7.11.0
dav: 1.33.0
deck: 1.15.3
external: 6.0.2
federatedfilesharing: 1.21.0
federation: 1.21.0
files: 2.3.1
files_accesscontrol: 2.0.1
files_downloadlimit: 4.0.0
files_external: 1.23.0
files_linkeditor: 1.1.23
files_pdfviewer: 4.0.0
files_sharing: 1.23.1
files_trashbin: 1.21.0
files_versions: 1.24.0
files_zip: 2.1.0
firstrunwizard: 4.0.0
groupfolders: 19.1.7
logreader: 4.0.0
lookup_server_connector: 1.19.0
mail: 5.5.6
nextcloud_announcements: 3.0.0
notes: 4.12.3
notifications: 4.0.0
oauth2: 1.19.1
occweb: 0.2.3
password_policy: 3.0.0
polls: 8.5.0
privacy: 3.0.0
profile: 1.0.0
provisioning_api: 1.21.0
quota_warning: 1.22.0
recommendations: 4.0.0
related_resources: 2.0.0
richdocuments: 8.7.5
serverinfo: 3.0.0
settings: 1.14.0
sharebymail: 1.21.0
spreed: 21.1.5
support: 3.0.0
survey_client: 3.0.0
systemtags: 1.21.1
text: 5.0.0
theming: 2.6.1
twofactor_backupcodes: 1.20.0
updatenotification: 1.21.0
viewer: 4.0.0
webhook_listeners: 1.2.0
workflowengine: 2.13.0

Disabled:

activity: 4.0.0 (installed 2.14.3)
admin_audit: 1.21.0
contactsinteraction: 1.12.0 (installed 1.8.0)
encryption: 2.19.0
files_reminders: 1.4.0 (installed 1.1.0)
forms: 5.2.1 (installed 5.2.1)
photos: 4.0.0 (installed 2.3.0)
richdocumentscode: 25.4.504 (installed 25.4.504)
snappymail: 2.38.2 (installed 2.38.2)
suspicious_login: 9.0.1
twofactor_nextcloud_notification: 5.0.0
twofactor_totp: 13.0.0-dev.0
user_ldap: 1.22.0
user_status: 1.11.0 (installed 1.1.1)
weather_status: 1.11.0 (installed 1.1.0)

aschrage · October 6, 2025, 5:05pm

I’m facing the same problem with the mobile browser Firefox 143.2 (62218), Nextcloud Server 31.0.9 and Mail app 5.5.6.

nomad · October 6, 2025, 7:40pm

Same here with Cromite Browser, I am tapping like crazy in the textfields and nothing happens. This applies when I create a new mail. When I reply to a mail, the keyboard appears, but then the next problem arises, the text field is too small, so I cannot see what I am typing.

But anyway I suppose the mail app (like most Nextcloud apps) is not made for mobile users, but desktop

Nextinger · October 6, 2025, 11:56pm

Thank you very much to both users for confirming the bug and providing additional details!

This appears to be a consistent problem with mobile input in version 5.5.6 that is not limited to a specific browser.

Summary of New Information for Developers

Confirmation: The bug is also occurring with:
- Firefox (Version 143.2 (62218)) on Nextcloud Server 31.0.9.
- Cromite Browser.
Divergent Behavior When Replying:
- When composing a new mail, the keyboard does not appear.
- When replying to a mail (Reply), the keyboard does appear, but the text field is too small, making the typed text invisible.

This suggests that mobile composition is generally flawed, but there are two different bugs depending on whether one is creating a new email or replying to an existing one.

aschrage · October 7, 2025, 4:33am

There is a related bug report in GitHub:

github.com/nextcloud/mail

I can’t write emails on the tablet with the onscreen keyboard

offen 03:48PM - 30 Sep 25 UTC

davodego

bug 0. to triage

### Steps to reproduce 1. Use a tablet with a 10'' screen 2. open Mail app 3. W…rite a new message 4. Click on the message text input field 5. the onscreen keyboard appears 6. The text field is pushed together by the onscreen keyboard so that the text I am writing is no longer visible. Scrolling is not possible. ### Expected behavior I can write text in the message field of the email. ### Actual behavior The text field is pushed together by the onscreen keyboard so that the text I am writing is no longer visible. Scrolling is not possible. ### Mail app version 5.5.6 ### Nextcloud version 32 ### Mailserver or service _No response_ ### Operating system Ubuntu 24.04 ### PHP engine version PHP 8.3 ### Nextcloud memory caching _No response_ ### Web server None ### Database PostgreSQL ### Additional info <img width="690" height="431" alt="Image" src="https://github.com/user-attachments/assets/da6dbd6f-c52a-4f09-91cd-9aed76f97f1d" /> <img width="690" height="431" alt="Image" src="https://github.com/user-attachments/assets/697ef28c-c94b-4bf8-885f-6320e33184fd" /> see also https://help.nextcloud.com/t/i-cant-write-emails-on-the-tablet-with-the-onscreen-keyboard/232588

Schmidtinger · October 7, 2025, 7:32pm

Good evening everyone,

I saw that Nextcloud Mail App version 5.5.7 has been released.

Before I install the update: Can anyone confirm whether the bug I described at the start of this thread has now been resolved in this new version?

Thanks in advance for your feedback!

aschrage · October 7, 2025, 10:18pm

The problem is still there with version 5.5.7

Mornsgrans · October 8, 2025, 7:03am

If you have a look on Github (see link to bug report above), you will find, that the report still is open.

Schmidtinger · October 13, 2025, 9:06pm

The problem ist still there with version. 5.5.8.

Nextinger · October 20, 2025, 10:50pm

Hello everyone,

I wanted to give a quick update on this thread, as I am still experiencing the issue.

I have now performed 4 app updates and have reached Mail App version 5.5.10. Unfortunately, the original bug concerning the missing virtual keyboard / cursor in input fields on mobile browsers still persists.

Best regards!

Mornsgrans · October 21, 2025, 9:42am

Please report it on Github (see link above).

Nextinger · November 26, 2025, 2:50pm

Hello everyone and Nextcloud developers,

First of all, on behalf of many users, I would like to sincerely thank the entire Nextcloud team for their great work and ongoing support! The platform is fantastic and a crucial pillar for data sovereignty.

Unfortunately, I must provide an update and emphasize the seriousness of the situation:

I can unfortunately confirm that the original issue concerning the missing virtual keyboard and cursor in the input fields of the Mail App on mobile browsers (when composing a new email) persists even in version 5.6.1.

This is an extremely critical bug as it essentially renders the Mail app unusable on mobile devices.

Appeal to Developers and Relevance for Data Privacy

Since this bug has now been present across several versions, it would be extremely valuable and reassuring for the entire community if one of the responsible developers, such as GretaD, kesselb, or Christoph Wurst, could briefly comment on the issue and perhaps provide an update on the current status or possible fix.

This bug is particularly relevant because many organizations that use Nextcloud specifically for data protection and data sovereignty reasons place great importance on not storing personal data (e.g., customer data, email addresses) on employees’ private mobile devices (smartphones/tablets).

Therefore, a fully functional mobile web interface for the Nextcloud Mail App is absolutely essential. Without this functionality, secure and data protection-compliant operation is severely limited. The core function of composing emails via the mobile browser interface of the Mail App urgently needs to be restored.

Question to the Community

Can anyone else who has updated to version 5.6.1 or a newer version confirm this error? Or—even better—has anyone found a workaround that we can use as a temporary solution?

Thank you for any reaction!

Best regards, Schmidtinger

Mornsgrans · November 26, 2025, 3:32pm

I can confirm it with Nextcloud 31.0.10, Mail app 5.6.1 on my Android 15 device with firefox 145.0.1
If I tap on “to:” field, it flashes 1 time as well as the text body field.

bb77 · November 26, 2025, 4:51pm

Hey ChatGPT, write a passionate appeal to Nextcloud developers like GretaD, kesselb, or Christoph Wurst, asking them to justify why their email client cannot be used properly in a mobile browser. Please use the full repertoire of bullshit bingo words and be sure to include the terms data protection, data sovereignty, and private. Thank you.

Oh, and please don’t forget to ask the community if there’s a workaround. Not that there’s likely to be one, and not that anyone is likely to read your slop this far, but it can’t hurt to ask.

Sorry, I couldn’t resist.

Mornsgrans · November 26, 2025, 5:47pm

I really don’t know, why you are reacting like that.
@Schmidtinger posted the same two hours ago on Github, too. So the developers got a direct feedback on the latest mail app version.

bb77 · November 27, 2025, 7:50am

Well, at least it’s in the right place then. But still, it’s an obvious bug and the developers have already acknowledged it. Who knows, though? Maybe this 300-word essay will somehow speed things up.

Seriously: I understand that the bug is annoying. But he could have made his point in a shorter and less obvious AI-generated way, don’t you think? And, ultimately, the post is still kind of ‘naggy’, isn’t it? Even if it’s nicely worded and wrapped up in grand rhetoric. But yeah, I get it’s important to him, and my post wasn’t meant to be taken too seriously either.

Anyway, a somewhat cumbersome workaround was posted in the relevant GitHub thread about 12 hours ago. Maybe it’s useful to anyone until the actual issue gets fixed: https://github.com/nextcloud/mail/issues/11774#issuecomment-3582755094

Mornsgrans · November 27, 2025, 9:32am

Good guy, who found a workaround.

Nextinger · November 27, 2025, 4:43pm

Thanks to mhst09 from the GitHub forum for the lifehack. While it’s not the perfect solution at the code level, this workaround works for now. Perhaps it can also be an important clue for the developers to find a way to solve the problem:

There’s a little lifehack for regaining focus and getting the editor working again. Click the three-dot button next to the “Submit” button, select “Text Blocks,” and then close the window that opens. The editor will work again. It’s clear that users won’t be happy about this, but at least it works.

@bb77 Thanks for bringing additional attention to this issue, even with inappropriate comments.

bb77 · November 27, 2025, 5:31pm

Happy to help.

Just to be clear, I wasn’t being deadly serious. But here’s a tip for next time: at least leave out the separators and the title emojis.

By the way, I use AI for translations too, and my posts are often far too long as well, but that’s because I’m a chatty person, and the original posts are usually already like that before translation.