BlackFrame is not a valid member of ScreenGui | LoadingScript, line 717
17,728(72.95%)
77(1.55%)
17,728(73.18%)
1.00
2. Visit
1,698(6.99%)
1,687(34.03%)
1,698(7.01%)
1.00
3. BlackFrame is not a valid member of ScreenGui | LoadingScript, line 658
1,242(5.11%)
6(0.12%)
1,242(5.13%)
1.00
4. BlackFrame is not a valid member of ScreenGui | LoadingScript, line 633
322(1.32%)
2(0.04%)
322(1.33%)
1.00
5. CoreGui.RobloxGui.Modules.PlayerList.Reducers.PlayerRelationship:46: attempt to index nil
with ‘isBlocked’ | CoreGui.RobloxGui.Modules.PlayerList.Reducers.PlayerRelationship, line 46 CorePackages.Packages._Index.roblox_rodux.rodux.createReducer, line 10 CorePackages.Packages._Index.roblox_rodux.rodux.combineReducers, line 15 CorePackages.Packages._Index.roblox_rodux.rodux.Store, line 89 - function dispatch CorePackages.Packages._Index.roblox_rodux.rodux.Store, line 53 CorePackages.Packages._Index.roblox_rodux.rodux.thunkMiddleware, line 12 CorePackages.Packages._Index.roblox_rodux.rodux.Store, line 62 CorePackages.Packages._Index.roblox_roact-rodux.roact-rodux.connect, line 130 CoreGui.RobloxGui.Modules.PlayerList.Components.Connection.SocialConnector, line 109 CoreGui.RobloxGui.Modules.PlayerList.Components.Connection.SocialConnector, line 43
Still consistently seeing this error in our upcoming game. It happens every time I load into our lobby place and produces exactly 500 errors every time.
I hope so. I’ve been getting this for the past few weeks. Always makes games take longer to load. Weirdly the topbar doesn’t show any of the icons and such, I can’t open the menu at all nor the developer console until they appear (didn’t catch that in the image below, but I’m sure others know about that too).
This bug also breaks the default loading screen (game’s creator username is not shown and the white “O” thing doesn’t spin). I’ll provide a video later.
With some errors I got about this, I think that’s because the error is from the actual Loading Screen, I still remember that I got a warning in the output, which has revealed that this error was from the Loading Screen, and because this error is from a script called LoadingScript.
If this error is resurfacing now, I would imagine that it has to due with the new topbar change but that doesn’t seem consistent with the error itself. The fix noted in release 421 is live, of course, but it seems that a new fix may be needed if its still happening.