10.2.6 Error - CSS preprocessing / aggregation fails, resulting in broken page / style

Same problem here :(

Looks like "/" are allowed only once in library names:

foreach ($libraries_to_check as $library) {
  if (substr_count($library, '/') !== 1) {
    throw new BadRequestHttpException('The libraries to include are encoded incorrectly.');
  }
}

And here is what I have this for $library in my case: asset_injector/css/fix_padding_top_exposition_slider

MR created.

Chose "." as the replacement separator.

Patch solved it for me as well. Thank you!

That fixed it for us, too. Thanks @mably! 🙏

Tweaked the title and summary a bit to add some context.

For reference, the changes that triggered this issue appear to have occurred in #3416700: Handle invalid compressed ajax_page_state more gracefully

Just ran into this after updating Drupal to 10.2.6.

I'm going to ping the maintainer as this is indeed critical and hard to find!

Furthermore we should open an issue in core for these things:

1. Find out if the if clause is correct, makes sense and really needed: if (substr_count($library, '/') !== 1) {
2. Add information about the failing library to the exception, otherwise the error is absolutely useless for site owners to find out what went wrong
3. I think the error message is misleading. I wouldn't think of an "incorrect encoding" if there's an unexpected "/" in the library name??

Reviewing MR...

Yes, this makes sense.
Adding attributions.

And released, and off:
https://www.drupal.org/project/asset_injector/releases/8.x-2.20

Thank you very very much for your super quick reaction @geek-merlin! 🎉🚀

Thank you @geek-merlin !

That was a nice fast fix! Thank you @geek-merlin!

Here's the follow-up in core: #3445072: Improve "The libraries to include are encoded incorrectly" check and message

I confirmed this fixes the issue for Drupal core 10.2.x (10.2.6), patch applied on asset_injector v2.17.0 (no update for this module, so using patch instead)

I haven't updated the asset_injector version, I need to stick to v2.17.0. I'm using a patch for that reason

Note: This error was so bad on 2.19 (Complete CSS collapse) as we updated to 10.2.6, and the fix with 2.20 so complete, it's my opinion only but I'd strongly recommend flagging 2.19 as no longer supported.

We didn't catch in in our local and our dev environments because JS aggregation was only enabled on prod.