Lets see if it happens at all with this post. When im typing, sometimes a bunch of text (a repeat of previously typed text) shows up after my cursor, but then goes away again if i keep typing. Except, sometimes all that text actually stays and i end up with weird double-speak in my comments. I’m gonna try and see that it takes to make it do it again. It seems to only happen when I’m tap typing (as opposed to swyping)
Seems it didnt want to actually do the part where it inserts the duplicates text.
Thanks for reporting this! I’m aware of the problem and I’m actively looking for solutions, but so far I haven’t found one.
It seems to be related to the new iOS17 predictive typing, because most often the duplication of text will happen when iOS tries to predict the rest of a sentence.
I’ll keep looking for a solution, since it’s quite jarring. Will keep you posted (:
I was thinking that was the issue, I first turned off auto-correct but the issue persisted. I’ve just now turned off “show predictions inline” and it seems to no longer be exhibiting the issue.
It’s particularly odd that I don’t recall having that issue in any other app. Is there something special about the way you’re formatting the text for that text field?
I think it’s a problem related to React Native. The package that I use for the markdown editing is a native iOS package, so I had to write a bridge for the package to be able to use it in my app.
Avelon uses the same package for example, but there it works fine as far as I know. Avelon is however a completely native app, therefor I have the suspicion that the problem is related to the bridge that I wrote.
I already tried to isolate the bridge, to see if any other code in my app is interfering but that didn’t seem to be the case. My plan is to write a dummy application somewhere this week, to see if the package does work out of the box in a native app to make sure that my suspicion is right.
I’m not too familiar with native iOS development though, so that’s why it’s all taking a bit longer.
It is however very helpful to hear that the prediction setting seemed to resolve it in your case. Bit by bit we’ll get closer to fix this 🤞