Emoji autocompleter sometimes leaves search string after replacement
See original GitHub issueDescribe the bug
When searching for an emoji via :
autocompletion sometimes it leaves the search text after inserting the emoji. It only happens occasionally but I’ve found one reliable way to reproduce it, see below:
To Reproduce
Steps to reproduce the behavior:
- Type
:tada
(it’s important to type exactly this) - Select the 🎉 emoji from the completer
- The message composer will now say 🎉
tada
Expected behavior
Tada text is removed
Smartphone (please complete the following information):
- Device: Nexus 5X
- OS: Android 8.1 (Lineage)
Additional context
- App version and store Schildichat
1.1.7sc33
(I think this reproduces with EA as well) - Using AOSP keyboard.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
6 Quick Fixes for Predictive Emoji Not Working on an iPhone ...
To do this: Go to Settings > General > Keyboard. Tap Keyboards, then select Emoji and swipe to the left.
Read more >iPhone Predictive Text, Emoji Not Working, How-To Fix
We love texting on our iPhones! So when predictive text or iPhone emoji keyboard stops showing up, we need a quick fix--and we...
Read more >How to fix predictive emoji keyboard not working on iPhone or ...
Open and tap General. Tap Keyboard > Keyboards. · Go to > Keyboard > Keyboards. If you don't see the Emoji keyboard here,...
Read more >Autocomplete is too eager and inserts suggestions even when ...
Tried running :mode() and searching for mode in the ale docs but came up empty handed.
Read more >Predictive Emoji Keyboard Not Working in iOS 13? [Fixed]
Some iPhone and iPad users have reported that predictive emoji keyboard is not working in iOS 13. Here are some possible solutions to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in 1.3.9
This still happens to me. It also happens in a more confusing way, that I just did:
On Thu, Nov 25, 2021 at 8:59 AM Adam Brown @.***> wrote: