Description
https://apis.roblox.com/notifications/v1/send-experience-invite is used whenever you invite a specific Friend/Connection through the In-Experience Invite Menu, where you’d usually have the option to generate an invite link, or invite a friend.
But there are cases where you invite someone and it doesn’t reach out to them. This happens if you’re inviting the same person within the same game you’ve already sent an invite from, regardless of JobId. There’s a cooldown for sending an invite per game, and I think per idempotencyKey.
When making a request to https://apis.roblox.com/notifications/v1/send-experience-invite it will return Status 200, even though the invite will never be shown to the user you’re inviting. This design causes unexpected behavior.
Re-production Steps
Detailed Re-production Steps is in Private Message.
- Join any game.
- Click the Roblox Logo Menu at the top left
- Send a friend an invite to your game
- Join another server instance within the same game.
- Re-send an invite
- Check whether the friend received the second invite.
Expected Result
If the Universal App displays to the user, that an invite has been sent. It should also actually “be sent” completely.
Actual Result
The Universal App displays that an invite has been sent, even though it didn’t send one completely if you were on a cooldown.
A private message is associated with this bug report