Next Gen Explorer has many annoying issues and bugs

Bug Reports Studio Bugs
,
#1

Looks like the Beta was automatically enabled for me, ever since then I’ve ran into a few issues that are quite annoying.

  • Doesn’t always scroll down after selecting an Instance during a Hierarchy search
  • Sometimes unable to expand by pressing the arrow button with my mouse (but using the arrow keys to expand fixed it)
  • Search history doesn’t register certain queries unless you press “Enter” to confirm the query, however in the old Studio I was able to use up arrow/down arrow to recall history, in new editor it annoyingly just goes over the suggested filter
  • Explorer crashed, had to restart studio. error:
ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:140: ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:117: 
------ Error caught by React ------
attempt to index nil with 'current'
------ Error caught by React ------
ExplorerPlugin.ExplorerPlugin.Packages._Index.Explorer.Explorer.Components.SearchBox.Dropdown:123
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberCommitWork.new:460 function commitHookEffectListMount
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberCommitWork.new:2200 function commitPassiveMount
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2829
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2810
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2810
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2810
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2810
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2810
...
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2970
ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.Scheduler:359 function unstable_runWithPriority
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.SchedulerWithReactIntegration.new:164 function runWithPriority
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2764
ExplorerPlugin.ExplorerPlugin.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:2559
ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.Scheduler:304
ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.Scheduler:260
ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:81 function doWork
ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:104 function performWorkUntilDeadline
  -  Standalone
  02:07:00.688  Stack Begin  -  Studio
  02:07:00.688  Script 'ExplorerPlugin.ExplorerPlugin.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default', Line 140  -  Studio
  02:07:00.688  Stack End  -  Studio
1 Like
#2

Do you think you can file these as separate bug reports? It would help significantly since we can only mark issues as totally closed or not.

Additionally, we need way more information on the first 2.

1 Like