I use the Fastmail android app on my phone (Moto G4, Android 7.0). Mostly it works fine, but if I edit text that I am composing (i.e. move the caret back into text I've already written and make changes), it goes badly wrong, corrupting surrounding words when inserting characters, to the point where it is impossible to continue editing. Adding text at the end of a paragraph seems ok.

E.g. compose new message, write "test message", then position cursor before the first character and type "real" followed by a space. About 30% of the time this corrupts the text, eg to "*messReal Testage". The corruption seems much more likely and more severe if I use the 'glide writing' Google keyboard feature were you trace out words without lifting your finger, but I also see it when doing normal tapping. I think it's always when inserting a space.

I'm using the default Google keyboard, in UK English. I've been experiencing this for many months, and my wife also gets it. I've only ever noticed it in the Fastmail app. For example, there is no problem composing text in Chrome. Though my wife says it affects the Facebook app too.

Has anyone else experienced this - in Fastmail or any other app? (I realise it might not be the Fastmail app's fault - though as I said personally I've only ever seen it there)

I had faced this issue with default keyboard (Google) and SwiftKey. However, I installed BlackBerry Keyboard from the Cobalt Manager and this issue is resolved completely. I think it had to do with the bugs in the keyboard rather than the app itself.

Let me know if you need any help with the BlackBerry Keyboard (which works almost perfectly) instead.

[quote=sebwills;603544]I use the Fastmail android app on my phone (Moto G4, Android 7.0). Mostly it works fine, but if I edit text that I am composing (i.e. move the caret back into text I've already written and make changes), it goes badly wrong, corrupting surrounding words when inserting characters, to the point where it is impossible to continue editing. Adding text at the end of a paragraph seems ok. /[quote]

Yes, got problem too. Only with FastMail app - gesture typing worked fine in other apps, although I don't have Facebook app. Typing email replies was tedious, particularly going back to a previous word to edit/add something. Happened with default android keyboard US or UK, and with SwiftKey. Gesture typing seemed too fast for the fastmail app 😕

I uninstalled the FM app. Now using web app only. Don't get email notifications, so others may not want that, but it's much faster on my moto g4+ with 2GB RAM. And RAM usage is way down. FM app would creep up to over 200MB. Web app Max 20MB. That said, my phone's total RAM doesn't get over 1.3GB, so I have no idea what's the issue.

It does seem related to the Google Keyboard, but it also seems unique to Fastmail. I can't change keyboards easily on the Pixel and don't really want to because I do love the GBoard in every other app.

Thanks to everyone for your responses. Helpful to know others are seeing the problem.

@radtux - could you explain how to get the Blackberry keyboard? Is it the 'Keyboard for Blackberry' app? That didn't look quite right from the description.

@mgg - interesting that you see it on a Pixel. Everyone who has the problem on this thread so far has had a Moto so I had been thinking it was something Moto-specific.

I did report the issue to Fastmail (ticket 368552) - the agent said they couldn't reproduce on their phone and suggested reinstalling the app, which I just tried - no improvement. I will follow up and point them to these threads.

I am coming to the conclusion that I should just abandon the app and use the web interface or another mail app. Getting frustrated with slow inbox loading and lack of offline access anyway....

......
I'll try the web interface again -- I used to use it, can't remember why I switched to the app.

<M>

Probably because the app has push - so you get notificaitons, but the web interface does not.

I find if I close FM on my phone, and then open it before I read or try to send an email, it more often behaves properly. Otherwise it usually hangs trying to connect to the server. I have also experienced the whacky/mangled text issue.

Probably because the app has push - so you get notificaitons, but the web interface does not.)

Myeah.... but that's not it -- we've turned off push and instead use the 'Pushover' service to create custom push notifications for only very specific emails; otherwise it would be craziness. Just tried the web app, and one of the other benefits is you can create shortcuts on the home page(s) to specific mailboxes or activities like 'compose'. That's actually great, because one of my peeves about the app was that it could not be set to open to a specified folder, only to the generic 'inbox'.

We've investigated and found this bug is happening in the Crosswalk framework that our app is built on, which unfortunately is no longer maintained. We need to move it to a different framework.

As well as suggesting using the web interface, they also pointed out that if you change the settings to compose plain text rather than rich text messages then the issue doesn't occur. (Settings -> Mail Preferences screen, under the Writing section.). Useful to know.

...As well as suggesting using the web interface, they also pointed out that if you change the settings to compose plain text rather than rich text messages then the issue doesn't occur. (Settings -> Mail Preferences screen, under the Writing section.). Useful to know.

I just tried this, and the problem remained, on my Pixel XL. Just FYI.