TextField RegisterValueChangedCallback doesn't fire on devices with IsDelayed set to true

When we updated from Unity 2022.2.5 to Unity 2023 or higher, our TextField.RegisterValueChangedCallback isn’t being fired properly on iOS and Android devices when IsDelayed is set to true on the TextField component. Desktop builds work fine. I can’t find any documentation about a change, or any other reports of this. Does anyone have any guidance there?

1 Like

Hello! Is this issue happening in play mode using the simulators too or only in builds?

I haven’t tried in the simulators, only on devices. It presents on both Android and iOS devices.

Sorry, I also realized I included the IsDelayed detail in the subject, but not the post. To be clear, the problem is when IsDelayed is set to true.

No worries, I tested with isDelayed set to true using the simulators and it works well. I’ll try on a device next.

Hello! Sorry for the delay, I was able to reproduce the issue, and it’s a bug indeed. I reported it and sent the repro project, it’s currently being triaged. I’ll update you when the bug is created so it can be tracked.

Thanks so much for reaching out!

Thanks Laila, is there any way to know a timeline to getting a fix for this? It is preventing us from updating to a version of the unity engine that supports Android SDK 14+, and Google Play has a requirement that apps be upgraded to that version before August 31st or risk having the app suspended on the store.

Hello!

The bug has reached the team and has been triaged, I asked about a possible timeline, and I’ll update you!

Thanks again for reporting!

I have this exact same issue, Unity 6000.0.31f1, targeting Android 35. Do you have an update on the status? I can’t release like this…

1 Like

A similar issue is also mentioned here:

It’s not just about IsDelayed property (which is broken indeed). There are several issues related to the virtual keyboard that must be fixed. I created a ticket several months ago which was confirmed by Unity team, but no news since then unfortunately…

Virtual keyboard is a basic feature used in many apps and it must be fixed asap imo !

I don’t understand how is this still unfixed.
This has been reported in July of 2024. This is a critical bug and essential UI functionality and it’s completely broken.

1 Like

This has been reported in July of 2024. This is a critical bug and essential UI functionality and it’s completely broken.

I absolutely agree.

Also, I did not find this issue in Known Issues: Unity Release Notes (Alpha) - Search

I am left with the impression that there are so many broken areas, even Unity cannot keep track of them all.

How is anyone supposed to create a stable product with such a broken platfom?
Underwhelming – as usual I must say.

Hi,

I have a project that has its whole UI implemented with the UI Toolkit. I really should update to Unity 6 a.s.a.p. but I can’t as long as this issue isn’t fixed - this is a game breaking bug!
Could your provide us with some details on when we can expect this to be fixed? I need this info for my own roadmap and to decide whether or not I should abandon using UIToolkit.

Thanks!