FFlagSTM5561Enabled9 issue, builtin_Toolbox.rbxm.Toolbox.Core.Components.Toolbox:294: attempt to call a nil value, recursivelyCommitLayoutEffects

Bug Reports Studio Bugs
,
1

Description

builtin_Toolbox.rbxm.Toolbox.Core.Components.Toolbox:294: attempt to call a nil value  -  Edit
  Stack Begin  -  Studio
  Script 'builtin_Toolbox.rbxm.Toolbox.Core.Components.Toolbox', Line 294  -  Studio
  Script 'builtin_Toolbox.rbxm.Toolbox.Core.Components.TabSet', Line 57  -  Studio
  Script 'builtin_Toolbox.rbxm.Toolbox.Core.Components.TabSet', Line 84 - function onClick  -  Studio
  Script 'builtin_Toolbox.rbxm.Toolbox.Core.Components.Tab', Line 44  -  Studio
  Script 'builtin_Toolbox.rbxm.Toolbox.Packages._Index.ReactRoblox.ReactRoblox.client.roblox.SingleEventManager', Line 112  -  Studio
  Stack End

Re-production Steps

I don’t know yet, it’s sort of mixed. I’d even try to re-toggle the flag on and off.

  • Turn FFlagSTM5561Enabled9 to get the previous Toolbox
  • Open a Studio Place
  • Click on the Creator Store tab
  • Click on a different tab
  • Click back to the Creator Store tab

 

It gives an entire error.

 

Expected Result

No error.

Actual Result

When you click on the Creator Store tab with the shopping bag icon, you’ll get an error and the entire Toolbox can also just disappear and error.

A private message is associated with this bug report

2

Hi @HealthyKarl,

Can you verify what version of Studio you’re on? You can do this by clicking “File” > “About Roblox Studio” and copy pasting the Version Number there.

Also to clarify, did you start having this error when toggling FFlagSTM5561Enabled9?

Screenshot 2025-05-30 at 1.51.02 PM
Screenshot 2025-05-30 at 1.51.02 PM454Ă—896 17.6 KB

3

Version 0.675.1.6750723 (64bit) but I was switching versions, so I don’t remember

FFlagSTM5561Enabled9 was enabled by default.

 

If I turn it off, I get the previous Toolbox without the Web View. But you also get the previous Toolbox without the Web View the first time you start Studio.

 

Looking at it I turned it off temporarily and then on again. I wanted to debug a different issue. I wanted to see if this Web View thing is using more resources compared to when it doesn’t use it. But I know I’ve turned this flag off before, and I haven’t gotten this issue when switching the tabs.

I updated the Re-production Steps.

 

e.g. when running a play test it uses the old one, but there it doesn’t have that issue

4

Got it. We’re removing FFlagSTM5561Enabled9 with the next Studio release, so this workflow won’t be supported anymore. We’re currently running some tests with the new Toolbox, but if you would like to use the old one you can turn off FFlagCreatorStoreWVEnableABTest2 instead. We can’t guarantee how long this workflow will be supported though.

Separately, if you noticed any issues with performance or with your workflow, please let us know.

1 Like