.Activated and MouseButton1Click not working for mobile users

[7z99 (cody)]

Yep, creating a new button does activate the .Activated event.

[SaifLachmann (Saif)]

You might wanna try your mute system inside the new ScreenGui to see if that works as well

[7z99 (cody)]

It doesn’t activate in the new ScreenGui.

[SaifLachmann (Saif)]

Do you have any backdoor breaking your scripts?

[7z99 (cody)]

No, I create all of my scripts from scratch.

[NotEphrem (Ephrem)]

Since it’s deprecated, I’m assuming this has something to do with the UICorner instance that you have under the button. This instance is pretty new to Roblox so it might be the case where they forgot to implement it with .Activated, it would explain why MouseButton1Click works as that’s the recommended method of sensing client input on a GUIButton.

[7z99 (cody)]

Yeah, it could be compatibility, however .MouseButton1Click doesn’t work either.

[NotEphrem (Ephrem)]

Confused now, If MouseButton1Click isn’t working, its either that the event is getting silenced as in the case when using ContextActionService or your code is never reaching that line that connects the event to a callback.

[7z99 (cody)]

I’m not using CAS, and it works on computer which is weird. I put all the info you asked for in post 16

.Activated and MouseButton1Click not working for mobile users

Sure, let me just get that ready. Here’s a screenshot of the hierarchy of PlayerGui. The localscript is where the button controller is. [Capture d’écran, le 2020-10-29 à 17.10.05] Testing on computer With mobile “emulator”: On my actual phone:

Full script is in post 4

.Activated and MouseButton1Click not working for mobile users

It’s not any better, MouseButton1Click is recommended actually. In any case to answer your question, I just ran a test and yes the Activated event seems to work just fine on mobile. Like I said there could be many reasons, some to consider would be the following: Are you using ContextActionService? Are you sure that you’re code to handle the event is even running? (aka are you sure it’s not yielding beforehand)

[NotEphrem (Ephrem)]

I see the issue now. It’s most definitely your Z-Index that’s messed up. Try setting the TextButton’s Z-Index to 10. This will make sure that your button isn’t fighting with other elements to be sensed on the screen. The behavior changes with mobile inputs too which would explain why it’s only working on PC.

EDIT: Make sure to mark as solved, when you’ve observed the behavior

[SaifLachmann (Saif)]

Yeah I totally agree with what @Zexali said I believe that your script isn’t really reaching the part where it connects into the .Activated event, as you said that it works on other scripts using .Activated

[7z99 (cody)]

I feel so stupid. It finally worked, thank you guys so much!

Basically here’s a summary of what I did (it’s too much lol)
Changed ZIndex
Changed Active to false on labels/frames
Changed Active to true on buttons
Changed Activated to MouseButton1Click

[SaifLachmann (Saif)]

Yeah it’s probably the stacking of multiple GUI elements, that sometimes messes up the GUI perspective for touch / mobile. Make sure to mark your post as the solution for other people to advantage of this!

[sjr04 (uep)]

btw it wasn’t necessary to change Activated to MouseButton1Click; @Zexali got the two confused. Activated is the recommended event.

@darthskrill

I will look into this. Btw does it seem to work if you use Activated event instead? This is the preferred way of listening to clicks with a mouse and taps with a touch. Eventually we will deprecate MouseButton1Click in favor of Activated

[7z99 (cody)]

It’s alright, as long as it works. I was getting so frustrated and couldn’t figure out why haha.