ContextActionService + FilteringEnabled BindAction Bug

If a place has FilteringEnabled set to true, calling ContextActionService:BindAction() will never create the button on iPad AFTER the first time it is created. For example, if you have a script that calls BindAction every time the character spawns, it will work the first time, but on the second spawn, it will fail silently.

These two places are identical except for this one having FilteringEnabled set to true.

Repro:

  1. Join this place on iPad https://www.roblox.com/games/422869094/ContextActionService-Test
  2. Observe that an empty button has been created. Clicking that button will light your head on fire.
  3. Reset your character
  4. Observe that when you respawn, the button will be gone and will not reappear, even though the BindAction function is called.

Now perform the same thing, but in the place with FilteringEnabled = false. It works just fine there. https://www.roblox.com/games/422882712/ContextActionService-Test-No-Filtering

I have no clue what is causing this, but it’s really strange. I already tested unbinding the action when the character dies, or before the call to BindAction, it has no effect on whether this bug occurs.

EDIT: Reproduced on Samsung Galaxy S3, so it’s not iOS specific.

1 Like

Also can confirm this bug on the NVIDIA Tegra K1 tablet.

1 Like

That seems really weird to me since CAS should be 100% client-side.

This should be fixed now. It was caused by the ScreenGui that contains the ContextAction buttons not reparenting itself when you respawned.

3 Likes