Android phone autocorrect no longer functions since latest update
Describe the bug Ever since I updated my app a couple days ago, my phone's autocorrect no longer replaces misspelled words as I type in the app, although it still provides suggestions. This significantly slows my typing on my phone since I need to manually correct every typo.
To Reproduce Steps to reproduce the behavior:
- Open a note
- Misspell a word
- Word does not get autocorrected
Expected behavior As I misspell words, autocorrect should replace them as it used to.
Smartphone (please complete the following information):
- Device: Samsung Galaxy S10
- OS: Android 12
- Keyboard: Samsung Keyboard
- Version v3.43.5
Interestingly, this seems to only happen on Plain Text notes when I tested this out. May I ask if you're able to confirm the same?
Unfortunately I'm not a premium user, so I can't test this on other note types, but on the other hand I can confirm that the issue is indeed happening on Plain Text notes.
I can confirm that this happens only in Plain Text notes, in all other note types (Rich Text, Markdown, Spreadsheets etc.) word suggestions / autocorrect work without problems. It is indeed slowing down typing on the phone quite significantly.
@vocux @Hunter-K13 may I ask which keyboard you use?
I tried the latest version using Plain Text with GBoard and it seems to be working fine.
I use the Samsung Keyboard
On Sat, Feb 25, 2023, 15:20 Myreli @.***> wrote:
@vocux https://github.com/vocux @Hunter-K13 https://github.com/Hunter-K13 may I ask which keyboard you use?
I tried the latest version using Plain Text with GBoard and it seems to be working fine.
— Reply to this email directly, view it on GitHub https://github.com/standardnotes/forum/issues/2217#issuecomment-1445196055, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABM6L62PX4ACZM5J3KFOI2TWZJSQXANCNFSM6AAAAAARJL6OJQ . You are receiving this because you were mentioned.Message ID: @.***>
I use OpenBoard.
Am 25. Februar 2023 21:20:27 MEZ schrieb Myreli @.***>:
@vocux @Hunter-K13 may I ask which keyboard you use?
I tried the latest version using Plain Text with GBoard and it seems to be working fine.
-- Reply to this email directly or view it on GitHub: https://github.com/standardnotes/forum/issues/2217#issuecomment-1445196055 You are receiving this because you were mentioned.
Message ID: @.***>
Hello,
I am also noticing this behaviour. The autocorrect functionality doesn't work with Plain Text notes, it seems to work fine with other note types.
Standard Notes v3.167.25 Android 13 OpenBoard keyboard
I have this issue too. I mainly use plain text notes.
Standard Notes v3.175.2 Android 14, Pixel 6 OpenBoard keyboard
Can confirm that the Google Keyboard Gboard works with auto correct....but who wants to use that privacy nightmare keyboard with a privacy focused notes app?!
I spent some time debugging this issue.
It still occurs in the latest version 3.183.32, and was introduced in 3.43.5.
I have modified the OpenBoard keyboard to do some debug output, that shows the InputType flags when the keyboard opens for a text note.
Since 3.43.5 Standard Notes incorrectly sends the flags TYPE_TEXT_VARIATION_EMAIL_ADDRESS and TYPE_TEXT_FLAG_NO_SUGGESTIONS to the keyboard, causing keyboards that respect those flags to show no suggestions or change their behavior in other ways.
I have attached a debug version of OpenBoard that outputs those flags to logcat to allow for fast reproducibility and testing.
I have also attached logcat output of Standard Notes 3.43.1 and 3.43.5, showing the correct and incorrect flags respectively, while opening the keyboard in a text note.
I hope these insights help in resolving this bug.
P.S. I did an experiment with Standard Notes 3.183.32. It turns out setting autoComplete="on" for the textarea returned in packages\web\src\javascripts\Components\NoteView\PlainEditor\PlainEditor.tsx stops the TYPE_TEXT_FLAG_NO_SUGGESTIONS from being included, and allows suggestions to show on OpenBoard. Don't know why autoComplete is interpreted this way in the app's context though, and I couldn't see where the TYPE_TEXT_VARIATION_EMAIL_ADDRESS could come from.
I am now using the "successor" fork of Open Board (https://github.com/Helium314/openboard), where the issue is completely fixed.
I have this same issue. Back then, support suggested I downgrade to version 3.41.10. Now, this version does not sync, and I'm forced to update. I'm disappointed to see that, after 1 year and 5 months, this and other issues are still unresolved.
- Device: Google Pixel 6a
- OS: Android 14 (build 2024032100)
- Keyboard: Native keyboard
- App version 3.192.4
Typing in Standard Notes
Typing in Proton Mail for comparison
I am also very disappointed. I have used this app for over 4 years because of how easy it was to sync work between mobile and desktop, but now it's practically impossible to use the mobile version without typing much slower than normal.
I am now using the "successor" fork of Open Board (https://github.com/Helium314/openboard), where the issue is completely fixed. @vocux Is the issue still fixed for you with OpenBoard (or HeliBoard after the name change)?
I still have this issue, using HeliBoard, I mainly use plain text notes.
Standard Notes v3.191.21 Android 14, Pixel 6 HeliBoard keyboard
Is there any way we can get the StandardNotes Dev's to engage with this issue? It's really making note taking on Android more difficult than it needs to be.
Oh bummer, it is indeed not working anymore on latest HeliBoard and latest StandardNotes (havent noticed it stopped working because I mostly create new notes on PC). But I'm positive it was working at some point after switching to HeliBoard.
@vocux There is an option on HeliBoard (OpenBoard fork) under "Text Correction > Always show suggestions". I have enabled this on my Pixel 6 and this has allowed me to use autocorrect/spellcheck on Plain Text notes in Standard Notes. Enabling that setting on HeliBoard hasn't caused any detrimental effects on other apps on my Pixel 6......so far! I'll see how it goes and report back if there are any issues.
I wish Standard Notes would just fix the issue, which seems to be that Plain Text notes incorrectly send the flags TYPE_TEXT_VARIATION_EMAIL_ADDRESS and TYPE_TEXT_FLAG_NO_SUGGESTIONS to the keyboard. As found out by @DjNDB