Notified staff about this, hopefully we can see a fix rolled soon. I can confirm I’ve had this problem too, it’s an internal bug.
That is probably your code and not this bug, could you share your code with me in a private message?
It’s a shame that the Roblox staff doesn’t pay attention to this bug report and that you have to bring it to their attention personally…
Yes, but no. While this is a bug and should be paid attention, it’s low impact, lower than other more important bugs I see them dealing with right now which is great because they are prioritizing worse things first.
Let’s cut them some slack, this is just a little bit of red text in the console, nothing we aren’t used to seeing from time to time anyway. 
Edit: My source for that is here.
1 Like
Yes, you were right. Messed something up without realizing it. Forgot to update my post here.
1 Like
This is still relevant. It seems to be a race condition with roact. If you only have 1 script in ReplicatedFirst and referencing it as game.ReplicatedFirst instead of yielding for the service, you can beat it. But if you have anything else it won’t load fast enough to beat roact mounting to the default loading screen.
1 Like
Thanks for the report! Fix coming soon. We’ll follow up when we have an update for you.
5 Likes
Update: The issue has been fixed!
5 Likes
I tested it by moving RemoveDefaultLoadingScreen() to a snippet after some yielding, and now the error mentioned in the OP is no longer appearing.
Thank you for your advice on resolving this bug.
PS: I wish all other Roblox professionals would also follow your example of reporting the solution in the original bug threads.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.