Publishing to a different game is completely broken

Bug Reports Studio Bugs
#1

As of ~10AM CST, we have been trying to update our game Tropical Resort Tycoon, and publishing to the game is completely broken, giving us error screens such as these:

CleanShot 2023-08-18 at 10.10.04@2x
CleanShot 2023-08-18 at 10.10.04@2x1920×1496 272 KB
CleanShot_2023-08-18_at_10.06.362x
CleanShot_2023-08-18_at_10.06.362x1920×1496 257 KB

We have tried:

  • Using “Save to Roblox as…”
  • Using “Publish to Roblox as…”
  • Using “Save to Roblox as…” from a local place file
  • Using “Publish to Roblox as…” from a local place file

None of which has worked.

We have also tried using several different accounts with our developers being in several different parts of the world, publishing using Mac / Windows machines, all with the same results.

11 Likes
#2

YES. This has been happening to me when I publish to places that are Team Create/collaboration enabled.

Very annoying. Doesn’t matter if nobody has been in team create for a long time.

This has happened for several days now. Maybe a week+

5 Likes
#4

Hi. Thanks for reporting. Is this happening consistently for you? Did you do anything different when you get the second screenshot vs the first one? For the first error, one thing to try is to have all collaborators refrain from using studio for more than one minute before doing the “publish to different place” and see if you get the same error. sorry for the inconvenience. this helps us debug

1 Like
#5

(I’ll pop in with my experience)

We definitely don’t have any collaborators in studio for hours+ prior to encountering this bug. But I think I have noticed that if I open Team Create, then close it out, THEN go and open the ACTUAL file I want to publish over the place with, then the publish will succeed. Can you try this @filiptibell and see if it works for you too?

So if this is the case, it seems as if it gets stuck thinking a collaborator is in studio, when in fact they are not

1 Like
#6

My business partner (@FlikterLinked) & I have been receiving the same issue. Only way we have been able to publish is by spam clicking the retry button till it works, usually takes around ~6 clicks before it actually publishes.

Hopefully this gets resolved soon.

2 Likes
#7

@badcc you are suggesting the theory because you think explicitly closing team create closes the “ghost” session. Is this correct?
Updates: we made some changes in our system and we would like to know if this is still happening.

#8

I’ve never seen that before, Sometimes I get errors Which annoys me but I’ve never seen it say “server is busy”

#9

This was caused by a new feature we added mid-august that has since been turned off. Given that we haven’t seen any new examples of this lately I’ll be closing out this bug.

If this issue pops up again please start a new thread about it in this forum. If you do, be sure to include a link to this thread in the OP so we know it is related.