UserInputService.TouchSwipe appears to be broken - iPhone & Studio Emulation

The UserInputService.TouchSwipe event is currently not firing, meaning I can’t swipe open the shop/chat in Crazy Cards.

This is affecting my iPhone 16 Pro (iOS 18.0.1), and all device emulation via my MacBook Air M1 (Sonoma 14.5).

This bug is presumably related to changes announced here: Updating TouchSwipe & Introducing TouchDrag Next Week

GuiObject.TouchSwipe appears to still be working as expected, and I’ve been told that a Redmi Note 7 (Android) is not affected by this bug.

Example Video: https://www.youtube.com/watch?v=NCOdKv8-JTY
Demo Place File:
demo-place.rbxl (58.0 KB)

Expected behavior

UserInputService.TouchSwipe should be fired whenever a mobile player swipes their finger, regardless of device and visible UI elements.

Hi Jotslo, thank you for reporting this issue. We’re aware of issues with the studio emulator not working properly with the new TouchSwipe/TouchDrag api changes and are working on a fix for that.

Looking at Crazy Cards on an iPhone 15 Pro Max (iOS 18.1.1) the shop seems openable with a swipe.

Our changes to TouchSwipe bring the iOS behavior to be in line with the Android behavior, so perhaps you’re looking for the previous bugged behavior on iOS where the event would fire before lifting your finger off.

If you try flicking your finger across the screen, lifting it up at the end of the motion, on your iPhone 16 Pro, does the shop open as you’re expecting on Crazy Cards?

If you would prefer an event that fires without lifting your finger off, the UserInputService:TouchDrag API will give you the behavior that used to only work on iOS, on all devices instead of only on iOS.

Hi @PotionSeller33, thanks for the quick response!

TouchSwipe still doesn’t seem to be working at all, unless I’m doing something wrong - here’s a video showing how I’m swiping:

TouchDrag does appear to be working and a suitable replacement in my case, so I’ll switch over to that event in Crazy Cards for now - thanks for the suggestion.

The bug will still be reproducible in the example place file I sent.

1 Like

I really appreciate you capturing that video. The behavior you’re seeing does look concerning. We’ll continue to work on our side to track down what might be happening there.

1 Like

I spotted an issue with an iOS specific flag override that looks to be causing the behavior in your video. Would you mind attempting to repro on your place after closing and reopening Roblox?

Everything appears to be working as expected now - thanks!

1 Like