ypeError: array_keys(): Argument #1 ($array) must be of type array, null given in array_keys() (line 280 of core/modules/views/src/Plugin/views/filter/InOperator.php).

Can we get a real issue summary here? When is this happening? What other modules are you using? Can you reproduce this on a clean Drupal install?

Just adding an isset() is usually just masking the real issue.

I have restored the standard issue template. Moving to 11.x, this needs to be fixed there first and then considered for backport.

Thanks for updating the issue summary, that helps. There are still questions from a maintainer that should be answered, "When is this happening? What other modules are you using? Can you reproduce this on a clean Drupal install?"

And I see that an exposed filter is used. There are many issues related to exposed filters, has a search of those issues been done to ensure this is not a duplicate? This search link → may help with that.

smustgrave → closed merge request !8358

can the steps be written out don't really follow adding the fields as steps. If no steps can be provided think this will be closed out.

I just (08 April 2025) had the exact same problem on Drupal 10.4.6, while testing the new development version of drupal/workflow (1.x-dev, the future v1.9) in a huge Drupal project.

I have a battery of behat tests (about 200 tests), which fail with the new drupal/workflow module version unless I apply patch #9 above. The patch also makes sense to me. I would backport it if possible.

I tried reproducing this on HEAD with Standard profile but I can't. One thing of note is the "Show groups in dropdown" option that's present in the screenshot in the IS does not exist in core so I wonder if this bug is coming from whatever module adds that?

To even hit the code that's being changed in the patch you need an exposed taxonomy filter that has the "Limit list to selected items" option checked with some terms selected.

If we aren't able to get a set of steps to reproduce this, this issue may be closed.