Starting at some point around August 4th-5th, Greenville has experienced a weird issue where UserInputService touch events (like TouchTap, TouchSwipe) just flat out do not fire. This issue is still happening now, as I tested on my iPhone 13 Pro Max, and in the Studio device emulator set to the “iPhone XR” preset. We also had a large amount of our playerbase report these issues, and still are.
No updates were made to the related code or interfaces. Downloading and testing an old version of Greenville where it definitely worked, the issue persists and these touch events do not fire.
The game that this happens on is Greenville, however we have made temporary patches so the core functionality of the game is still playable for the users affected by this issue:
Some portions of the game are still broken (like our Criminal interactive job, where you would break safes open, which uses TouchTap that we could temporarily change to Activated with a TextButton to fix the issue).
This happens both with the global variant through UserInputService*** and on individual GuiObjects.
EDIT***: I’m not sure how I messed up during testing, but the global variants with UserInputService DO work, and I believe the culprit for this bug is found. See the replies from silicon_Aamir below.
I have tried:
- Reverting to a version of the game that it used to work completely fine, but the issue still persisted somehow
- Changing the affected TextButton’s ScreenGui to be the first in the display order, if it was some sort of overlap issue
- Toggled all common problematic properties like Active, Selectable, etc, and it would still not fire
- Deleting ALL other ScreenGui objects, assuming they could have some sort of overlap issue
- Deleting ALL BillboardGui and SurfaceGuis in the game to see if it would fire
- Changing all properties in the affected TextButton/ImageButton(s)
None of these above troubleshooting steps solved the issue.
If it matters, the system I first observed this issue on is:
Windows 11
Intel i9-13900K
32GB RAM
RTX 4090 FE
An important detail: These events work fine when tested on a blank baseplate and a simple ScreenGui and TextButton, and I’ve tried creating a separate script, or used the command bar in Studio and output (shown in GIFs below) in case it had to do with our code. We also have different areas in the codebase that use these events and they still do not work.
Here’s some GIFs if needed of me trying to demonstrate what is happening, but I believe it’s quite self-explanitory:
Expected behavior
TouchTap and TouchSwipe (and likely other events) should fire normally.
A private message is associated with this bug report