Game Publishing Failure Bug

HooferBevelops · August 4, 2023, 7:48pm

Issue

Whilst working on our development sub-place for our game, we have suddenly become unable to publish. This issue is not consistent, and we have not been able to create an exact reproducible instance other than for our game. The issue occurs for all of our team, however, sometimes not all at once. There are times where one of us can publish, but the rest of us three cannot. Sometimes, three can, only one cannot. This has become a major issue for us, as we are not able to publish patches for our game at all.

The issue has happened on both Mac and Windows.

Reproduction Steps

Open a sub-place of a Roblox game
File > Publish to Roblox As…
Select the primary game for the sub-place
Save & Publish will fail
Any future attempts of publishing as publishing to the sub-place rather than to the primary game.

Primary Game:

Development Sub-Place:

IDs for Users unable to publish: 1182777055, 114446765, 406236

I do not know how to safely attach a log file, but I will attach an excerpt here that has no harmful information:

2023-08-02T19:39:18.037Z,62.037197,1f278,12 [DFLog::HttpTraceError] HttpResponse(#880 00000157A1EBDFA0) time:9486.1ms (net:9486.1ms callback:0.0ms timeInRetryQueue:0.0ms)status:500 Internal Server Error bodySize:75 url:{ "https://data.roblox.com/Data/Upload.ashx?assetid=9938675423&issavedversiononly=false" } ip:128.116.114.4 external:0 numberOfTimesRetried:0
2023-08-02T19:39:18.042Z,62.042187,1de44,6 [FLog::Output] Oaklands - Staging publish failed.

Expected Behavior
To have the game successfully publish.

Actual Behavior
The save fails to publish, with future attempts not working.

RobloxStudioBeta_3hWw0SV8wG

Workaround
As of now, I have no work-around. Our team has tried flushing our team-create session, publishing separately, reinstalling studio, to no prevail. There are times where some of us can publish, and that becomes the reliant workaround.

Issue Area: Studio
Issue Type: Backend
Impact: High
Frequency: Often
Date First Experienced: 2023-07-31

thirdtakeonit · August 10, 2023, 3:53pm

Thanks for the report! I filed a ticket in our internal database and we’ll follow up when we have an update for you.

goofysufi · August 10, 2023, 6:41pm

Hey @HooferBevelops ,
Sorry to hear that - is this still an issue?

goofysufi · August 10, 2023, 6:43pm

Also do you mean any time you try to do Publish AS afterwards it will also fail?

Yume_Akizuki · August 10, 2023, 7:40pm

I’ve had a similar experience to this when I opened a new studio window to grab a script from another place.
The first place I had open had me ask to log in when I pressed F7.

Though this was a week ago, thought this extra info might be helpful.

Edit: the only fix was to entirely reopen studio.

HooferBevelops · August 10, 2023, 9:49pm

I haven’t done multiple publishes in a few days, but I will be able to let you know tomorrow if I can reproduce it still.

HooferBevelops · August 10, 2023, 9:51pm

In all cases, we only use Publish AS. Apologies for the bad explanation and typo.

I think that after the first failure prompt, any future attempt would try to publish to the sub-place being edited, rather than publishing to the main place. It was very unpredictable and I could not get consistent behavior.

Our team noticed that we would get two different messages after that first prompt. We would know it was successfully published if it said that we were still editing the sub-place.

When it did not work, it would just say Published new changes to “Oaklands.”
RobloxStudioBeta_Y1EoRu2J5a

This seems like a separate issue that occurs when a publish as fails to process.

On rare occurrences I could re-open studio for the unwanted behavior to stop, but it was not consistent.

KinderDev · August 10, 2023, 10:02pm

Another Oaklands developer here experiencing the same issue sometimes when we’re trying to push our updates, here’s an additional screenshot which may be useful:

bvetterdays · August 10, 2023, 11:05pm

This same issue has been happening to multiple developers including myself in the past few days. Yesterday it didn’t occur, so it may have been resolved, but when it does it’s a huge issue for me - preventing me from publishing updates at all.

1billybob1 · August 11, 2023, 1:19am

I was also having this issue, now it’s even worse:

Edit: After resetting studio a few times, I’ve been able to get to this issue again, which seems to be the overall post reasoning:

HooferBevelops · August 11, 2023, 4:19pm

Update:
I was able to reproduce the problem again today. It happened after we initially published the first time. From what our team has seen, we are able to do one publish before it completely locks up on us.

OfcMeowMeowFuzzyface · August 11, 2023, 11:24pm

Thank you for the report. We’re looking into it now.

goofysufi · August 12, 2023, 12:16am

@HooferBevelops

I think that after the first failure prompt, any future attempt would try to publish to the sub-place being edited, rather than publishing to the main place. It was very unpredictable and I could not get consistent behavior.

Do you mean after first Publish As to your production place, any consecutive Publish As to your staging place actually publishes to your production place? Or are you saying any Publish publishes to your production place (even though it should be your staging place)

HooferBevelops · August 12, 2023, 12:26am

Our first Publish As to our production place goes through. Any time we try to Publish As to our production place again, it would not go through.

We are trying to publish from Staging Place → Production Place. It will work the first time, but any time after will fail with an internal server error according to log files (in initial post). Expected behavior is for it to go through to Production, actual behavior is that it does not go through at all.

Initially, we thought it went through specifically to our staging, when our target was production, but that appears to not be the case.

goofysufi · August 12, 2023, 12:28am

Got it. Okay we’ll investigate why this is happening, this is unexpected for sure.

GeneralTso58 · August 12, 2023, 12:39am

just to confirm. when the subsequent publish from staging place to production place fails, you get a 500 log error and "Published new changes to “Oaklands.” in output window.

HooferBevelops · August 12, 2023, 1:15am

Yes, this is what happens when it fails.

bvetterdays · August 12, 2023, 5:30am

Yup, I’m also experiencing this issue again. From what I’ve seen, it happens at certain times each day and also occurs with “Save to Roblox as”. Very weird.

Tomi1231 · August 12, 2023, 7:19am

I’ve had some publish attemps fail, but I also got a lot of model publishing fails as well. Some times, I had to retry publishing a lot of times before being able to publish

GeneralTso58 · August 15, 2023, 12:32am

Hi. Thanks for the report. just to confirm, are you seeing the bug where after you publish from place A to place B, subsequent publish from A to B fail with 500 in the log and output window reads “published new changes to place A”?