Describe the bug
Typing more than one character when using the @ mention option in an Object causes the create/link object option to close, preventing me from linking an existing Object or creating a new one.
Steps to reproduce the behavior:
- If I type @, the “+ create new object” option is greyed out which makes sense as there is no name for the new object yet.
- Then, when I type one character (which should be enough to create a new object), but the option still is disabled
- Then, when I type one more character (so a second character) the whole menu disappears.
I can create a new Object or link to an existing object when typing more than a single character when using the @ mention option.
The bugfix is expected in 0.9.0
Still present in Anytype for Android 0.10.0.
Are you able to reproduce this bug in 0.11.0?
I still experience this on 0.11.0
This issue has been added to our issue tracker and was received by the Development Team.
Fresh install of 0.11.0:
Note how I try to @-mention the “Inbox” Set Object. The first time I can type the “I” and the relevant Object is shown. After typing the second character the options disappear. The second time, the list is not properly updated after typing the first character (you still see “create object @in”),and the third time is the same as the first time I tried, but now with type @ on the keyboard instead of the @ in the Anytype menu.
Very odd behaviour, but let’s fantasize then
Sam, can you confirm such behaviour with gboard or hackers keyboard? and what keyboard do you use?
Maybe you can confirm this behaviour on desktop 0.11?
Maybe you have an iphone to confirm?
And probably it can be related with the way we detecting that change. Your phone model maybe has some troubles with interacting with hardware or aosp
I use SwiftKey, but I’ll try another keyboard.
I’ll try on desktop 0.29.1
I’m running Android 11 on a Fairphone 4, which uses vanilla/stock Android
Edit: issues cannotbe reproduced with GBoard!
Great to hear, would be nice if we can sort out why there’s adversity to Swift-key but otherwise I think we can resolve this topic as circumstantial.
Thanks @fat_fellow for your help with trouble-shooting!
Tried with SwiftKey.
A problem is Microsoft Key board is reporting wrong amount on symbols in the framework method.
MS keyboard reporting a string length instead of a length of changed symbols. Our internal mechanism should be reworked to simplify the way it is working, but at least I am happy there are workaround. Thank you!
reference issue in our internal tracker to not lose it