Input issue

[ExarKunRevived]

Fly Casual Release Version
Which version did the bug occur in?
Newest version as of 2/7/25
Online Game Mode
Yes/No
No
Describe the bug
A clear and concise description of what the bug is.
When trying to clear existing text, i.e. IP Address input, Name, etc... error message comes up after second use of backspace. Freezes input and won't allow new input or continued clearing of preexisting text.
To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.
Text to clear and enable new text to be input into the window
Screenshots
If applicable, add screenshots to help explain your problem.

Platform/Device (be as specific as possible):

• OS: [e.g. Windows, Mac, Android]
• Version [e.g. Windows 10, iOS22]
  Android 14
  Additional context
  Add any other context about the problem here.

[Baledin]

Thanks for posting. I saw a slew of these show up in the crash reports but best I could tell was an input field, somewhere, was having an issue. I'll take a peek at it!

[Baledin]

Do you happen to know if this was an issue in v2.5.20241101.03? I don't recall updating the UI assets but this appears to be a core Unity UI issue.

[ExarKunRevived]

Yes this was. Both I and a friend downloaded FlyCasual-v2.5.20241101.03-Android.apk and both experienced that same input field error.

…

On Tue, Feb 11, 2025, 18:00 Jeremy S. ***@***.***> wrote: Do you happen to know if this was an issue in v2.5.20241101.03? I don't recall updating the UI assets but this appears to be a core Unity UI issue. — Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPI2GMYG7ACEUENLW2RHYVL2PKTLNAVCNFSM6AAAAABWXDJGKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJSGQ3TENRVGA> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: Baledin]*Baledin* left a comment (Baledin/FlyCasual#135) <#135 (comment)> Do you happen to know if this was an issue in v2.5.20241101.03? I don't recall updating the UI assets but this appears to be a core Unity UI issue. — Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPI2GMYG7ACEUENLW2RHYVL2PKTLNAVCNFSM6AAAAABWXDJGKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJSGQ3TENRVGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Baledin]

Thank you,

It doesn't look like there's a core fix for this--Unity has actually moved away from the InputField object used here and use a new TextMeshPro-InputField. I think I'll upgrade these fields and see if that resolves the errors.

[Baledin]

The previous work done on this did resolve the error but I'm running into issues getting the peer to peer networking working to test--I assume it's been working otherwise for you? I know I had tested it back when I turned it on and I haven't done anything explicitly with the networking components since so unsure why I can't get a valid test set up now.