TextBoxes typing problem

Bug Reports Mobile Bugs
#16

Bump. Players are still experiencing this issue on mobile.

EnterUI.TextBox:GetPropertyChangedSignal("Text"):Connect(function()
	EnterUI.TextBox.Text = EnterUI.TextBox.Text:sub(1,240)
end)
4 Likes
#17

Solution, check the length of the string before cutting it.
string.len

1 Like
#18

Still happends with my players. I’m sure this happens if your code is

textbox.Changed:Connect(function(a)
   if a == "Text" then
     textbox.Text = textbox.Text
   end
end)

Although I’m not exactly sure why this happens. But this happens on certain types of devices. My Android phone does not have this problem. Many players of my games complain about this problem, but due to its nature, I cannot solve it. I work with text fields very closely so this is necessary for me. I know about workarounds, but I don’t think it’s very nice.

3 Likes
#19

Can confirm this also happens in all my games where the textbox’s text is overwritten as the player is typing (on mobile). This impacts the user experience tremendously as some of the games I work on rely on user input!

1 Like
#20

I can confirm this still happens (I have no screenshot however)
On device iPad (10th generation) running iPadOS 17.3 (this isn’t a public beta)
Just typing your name in The Presentation Experience when you join is extremely buggy. I wasted Robux on Write the next subject because my subject didn’t type properly

1 Like
#21

I have a game in which this bug is very clearly visible. Also, on the Android system, when using auto-correction, the on-screen keyboard crashes and can no longer be used. You have to restart Roblox or even your phone.

The Game

Keyboard crash video on Android:

For some reason it only works in this game. It uses Roact library to display the GUI, but I don’t know how that might relate to what’s going on.

If Roblox staff has problems with how to reproduce this bug, they can try playing this game.

3 Likes
#22

I found a workaround of keyboard crash on Android. I made some debounce for changing event.
It’s looks like it:

local debounce = false

textbox.Changed:Connect(function(a)
   if a == "Text" then
     if not debounce then
       debounce = true
       textbox.Text = textbox.Text
       task.wait()
       debounce = false
     end
   end
end)

But now auto-correct is unstable and overall it’s not an ideal solution for this. But I’m sure that this is due to the event cycle, which calls itself due to text changes. (This happens naturally when using auto-correction)

1 Like
#23

Can confirm this is still happening. Honestly I might just make my own custom keyboard when I detect users are on mobile

2 Likes
#24

Still happens. Please fix this as my game heavily relies on textbox input.

1 Like
#25

Still Happening! Its been a while we are all complaining about it! Please do something!

1 Like
Mobile Text Input GetPropertyChangedSignal Bug
#26

It happens to me as well, in only some specific games. (Sorry for the bump)

#27

Hi all! I’m trying to reproduce this issue but having a difficult time. Is it literally just typing in a TextBox and using auto correct on mobile where this issue is triggered?

If someone could share a place file that reproduces the issue that would be very handy. Thank you!

#28

I was able to reproduce this problem on Android using the Roact framework, in which I create a input field and process the state when editing text. With a 25-35% chance, when using auto-correct, the text can be reset to its previous state, although if you look at the state update code, this should not happen.

I also reproduced this behavior on the Roblox menu located in CoreGui, This way you can make sure that the problem is not in my code.

Repro place.
Typing Bug Test.rbxl (123.7 KB)

Video.

I can’t say exactly what exactly is the reason for this behavior, but I can assume that Android and iOS use their own system input fields (API controls), and because of this there is conflicting behavior with the Roblox input field, we can say that there are 2 different field objects that interact between itself, and perhaps the .Changed event causes a false positive. I can’t be precise because I don’t know how it works in the Roblox engine.

1 Like
#29

Followup on this, found a decent workaround

  1. detect changes on the textbox with runservice heartbeat instead of using propertychangedsignal

  2. on each heartbeat step, if the textbox text is the same as the potential edited text, skip it. Otherwise edit the textbox text to the new values

That should do it and I tested it on several devices with several different parameters (only numbers and char limits) and it doesnt make the textbox go crazy anymore.

You can also obviously optimize it so you only run the heartbeat step if the UI is visible, etc. This should suffice until roblox fixes the getpropertychangedsignal stuff

#30

Thanks @pozzzy333 and @Zenith322 for providing this additional info. We have been unable to reproduce so far but are still investigating the issue. Hopefully we can provide updates soon regarding a fix. Thanks!

#31

Is there any update on this being fixed yet?

#32

Hello, i think this bug affect some types of devices because my new Samsung phone is more stable on this.
Here’s my impacted device:
Redmi Note 8T
MIUI Global 12.5.6 Stable

1 Like
#33

Based on some observations, I can assume that the bug with duplicated characters on mobile devices occurs during a short lag or low FPS.

1 Like
#34

Hi folks, thank you all for your patience.

We currently have a fix in progress that should solve many of the issues related to setting the Text of a TextBox within its change signal / within react state. We will be continuing to monitor and follow up on any issues that are still present after the fix rolls out.

2 Likes
#36

Hi folks, thank you for your patience. We’ve rolled out a fix for this. Please feel free to follow up if you’re still seeing issues.

1 Like