TeleportService:TeleportAsync fails due to "A specified Member cannot join the Destination Place" error

For the past few days developers have been encountering the error “A specified Member cannot join the Destination Place” when teleporting a group of players to another place.

I’ve also experienced this error yesterday while trying out the new party feature, however I don’t have any data to back this so take it as an anecdote.

Calling TeleportService:TeleportAsync() with a table containing multiple players as the players argument throws the error A specified Member cannot join the Destination Place, while it’s not thrown when teleporting a single player.

I’ve created a repro place to test this. The subplace is published and the other player has play access to it.

My place is private, however another user is encountering the same issue and his place is public.

Repro code (ServerScriptService):

local TeleportService = game:GetService("TeleportService")
local event = game.ReplicatedStorage.TeleportEveryone

event.OnServerEvent:Connect(function()
	print("Teleporting")
	
	TeleportService:TeleportAsync(91256466420414, game.Players:GetPlayers())
end)

Another instance of the issue: Teleport service error.

7 Likes

I’m experiencing this issue too. For me, it’s happening when I’m trying to teleport people with “Play” permissions in a privated game to a subplace of that same game. If everyone in the server has “Edit” permissions, the issue doesn’t happen.

6 Likes

Thanks for the report. We’ll follow up when we have an update for you.

1 Like

Seems to be occuring for TeleportPartyAsync as well. I am also experiencing this in my game which is set to private.

1 Like

Also having the same problem with TeleportPartyAsync and TeleportAsync. works fine if everybody teleporting has edit access though.

1 Like

You shouldn’t use TeleportPartyAsync().

This method should not be used for new work; the numerous teleport functions have been combined into a single method, TeleportAsync(), which should be used instead.

2 Likes

this is still happening to me, is it still happening for anyone else?

1 Like

Still happening for me. It works if everybody that’s teleporting has edit access, so for now I’m managing by just testing with other developers. Still quite annoying however, I hope it is fixed soon.

1 Like

Yeah, it works if they have edit access, I just tested it. I don’t know how this has been going on this long without a fix.

2 Likes

Seems to be the same issue for me as well. Bump

1 Like

I wonder how this hasn’t impacted any major game. Could there be a specific edge case or did they find a workaround?

I haven’t tried any major game like piggy or anything, I wonder if it is also affecting them aswell.

This issue only happens in privated games where people are given Play access

My games public and this happens.

1 Like

No, it also happens in public games as you can see in the topics I linked in my OP.

A potential workaround you could try is wrapping the initial teleport function that presumably tries to teleport all players in a pcall. That way you should be able to detect if the group teleport fails for whatever reason. Then potentially run a fallback teleport attempt that runs TeleportAsync on each player individually through an i, v in pairs loop.

local TeleportService = game:GetService("TeleportService")
local event = game.ReplicatedStorage.TeleportEveryone

event.OnServerEvent:Connect(function()

local success, err = pcall(function()
	print("Teleporting")
TeleportService:TeleportAsync(91256466420414, game.Players:GetPlayers())
end)
if not success then
warn("Group teleport failed, attempting fallback method, error was: "..err)
for i, v in pairs(game.Players:GetPlayers()) do
TeleportService:TeleportAsync(91256466420414,{v})
end
end
end)
1 Like

I think its fixed, my party is teleporting correctly.


.
.
Still buggin. I got this on the test place just a minute ago.
Public game with editable rbxl. Have a look.

Huh, it was working fine yesterday. Ill see if its broken again today.

Any update on this? This is preventing our team from releasing a critical update.

1 Like