10.3.0 core state services changed

I see it's fixed in v2.0.0.
I've updated.

The problem is v1.1.6 was compatible with 10.3 drupal.
Than my patch is not a solution.
We need to deny d10.3.0 from v1.x with composer.

We need a solution that works for both, 10.2 and 10.3 - I thought we had addressed that, but maybe forgot for the 1.1 branch. I'll have a look.

For reference, this is the issue where we were supposed to have fixed that for 1.1 already: 📌 Add support for cache collector for state in core Active

Not sure why that didn't really work out as intended.

Please have a look into the MR!432 whether that fixes the issue for you. Ideally, if you could test this for both Drupal core 10.2 and 10.3?

This is trying to declare ECA's state service independently instead ob using the core state service as a parent.

Hiding the patch.

Great idea.

I've tested and works well with 10.2.7 and 10.3

Thank you!

Thanks for quick testing. Tests are passing too.

Just about pushing 1.1.7

Automatically closed - issue fixed for 2 weeks with no activity.

Hello,

I've done the upgrade to 10.3.1 drupal core and ECA 2.0 and the error is persisting.
I've applied the patch but it doesn't work.

can you help me?
Thank you

@ sazevedo@ua.pt

I have version 10.3.1 and ECA 2.0 and the error is gone. For 10.3.1 (and for 1.1.7) you do not need to apply the patc anymore.

Thank you Daniel, at the end of the day we manage to do the upgrade without any error.

That's great.

This solution worked for me.