The function Player:IsFriendsWithAsync() consistently returns false even when using a valid UserId from an existing Roblox Connection. The same behavior occurs with deprecated functions such as Player:IsFriendsWith() and Player:isFriendWith().
This happens in both LocalScripts and ServerScripts, but only in live servers — in Roblox Studio, everything works as expected.
However, something strange also happens: the function returns true if the Connection is currently in the same server, but as soon as they leave, it starts returning false.
Steps to reproduce:
Join a live game server with a Connection.
Call Player:IsFriendsWithAsync(connectionUserId) from either a LocalScript or ServerScript.
Have the Connection leave the server.
Observe that the function now returns false.
Expected behavior
The function should return true even if the Connection is not in the same server.
I saw someone else mention this problem a few mins ago in a discord development server (unless that was you lol) - but def sounds like a bug, I haven’t checked it - (not helping sorry) but was just interested since I’ve now heard this twice today
The team has completed the patch. The patch should go live later next week (around February 26th) and be fully adopted by all clients in early March. I’ll post a follow-up message in this thread if the release timelines change.
Thank you for identifying the solution – we’ve also been dealing with many player reports who are trying to join friends for Gacha Online ✨ RP - Roblox .
Is there a reason this can’t be patched separately and sooner? Especially since it’s already been resolved and a solution found. Waiting another 9 days for a patch is going to cause friction with our playerbase.
The team just rolled out the fix to all platforms excluding iOS. iOS release was slightly delayed this week. I will update the thread once the patch is applied to iOS. In the meantime, please let me know if you continue to experience the bug on other platforms.
iOS rollout is complete, although iOS adoption is not 100% yet. You can check if a client has the change by going to More Tab => About => App Information and checking the second part of the version. Versions 710 and above have the patch.
@A_DMINING we are unable to reproduce the issue internally on windows. There are still a small percentage of windows clients that are on 709. It could be that your client has not picked up the update yet. If your client is on 710, it would be helpful to know the steps you used to reproduce the bug.