Issue with Event RSVP Prompts on Mobile Devices

When using the new Event RSVP Feature using SocialServices, the Event RSVP Prompt does not resize correctly on Mobile Devices. I’ve attached an example of what my screen looks like when trying to Prompt myself to RSVP for Upcoming Event.

Expected behavior

The Prompt should dynamically resize itself based on the screen resolution of the Users to clearly showcase all relevant information, images, and Buttons. Behavior should emulate all other Default Roblox Prompts, just like Friend Invite Prompts, Asset Favoriting Prompts, Experience Notification Prompts, ect…

4 Likes

Hey, sorry about this issue, and thanks for the report.

There was a bug in our code that was supposed to clamp the size of the prompt, meaning it doesn’t work correctly in all circumstances. We have made this code much more robust and hope to release this fix soon.

Here is what this looks like with the fix:

Can you share the eventId of this event so I can test it and ensure it scales correctly and looks good on various device sizes?
Thanks!

3 Likes

Not OP, but I’m seeing the same issue with event ID 4707138414623588710 if you want to test with that.

2 Likes

Hey thanks for the follow up, seems like you’ve fixed it! Please try my Event ID (4283187419326185737)!

1 Like

Do you know when this fix is planned to roll out? No worries if not, I am just wondering as I want to put a banner in-game before an event later this week.

I can’t wait for the bug fix to be released. :star_struck:

Unfortunately, I wasn’t able to get the fix out as fast as I would like but I hope to be able to release it early next week.

1 Like

Sadly. I wanted to increase the number of players at my upcoming game update event on Friday.

I found that the bug only applies to phone players, not tablet or any other platform. As such, you can still boost the event by showing the RSVP prompt to those players.

There’s no built in way to check if a player is phone or tablet so this may not be 100% reliable, however I found that the following method was accurate for all the test cases I tried:

1 Like

I’m seeing the same issue with event ID 8626961393427153125

The fix for this issue has been fully rolled out. Thanks again for your report.

1 Like