CollectionField to another relation on detail page is calling EDIT action on crud controller of relation

[siggidiel]

Describe the bug
I have two entities which have a OneToMany relation -> EntityA (one) <--> EntityB (many). On the DETAIL page of my EntityACrudController I am using a CollectionField::new('relationalField'). This is causing a crash of my application, because it calls the EntityBCrudController's EDIT action, where I am using the AdminContext to receive the entity instance, which is null in that case (it is working perfectly fine if I visit the EDIT page of EntityBCrudController directly).

Why is it calling the EDIT action of the crud controller of my other entity???

This is happening after I updated EasyAdmin to version 4.29.1.

Btw: I am not using the useEntryCrudForm() method on my CollectionField. And I am not using pretty URLs

[siggidiel]

After some debugging, I found that the issue comes from the CollectionConfigurator. This change could be the reason:
801e815#diff-100aaf7a11a06c600ef2c48bb42aa90c85ed6253721bf953770dbed7bdda8224

The method \EasyCorp\Bundle\EasyAdminBundle\Field\Configurator\CollectionConfigurator::createEntityDto is causing this issue. Inside, the line $this->fieldFactory->processFields($entityDto, new FieldCollection($fields), $crudPageName); is being executed with with $crudPageName value edit for my relational crud controller. But why? I am on a detail page.

[siggidiel]

I started downgrading EasyAdmin from version to version. Reaching version 4.28.0 the relational crud controller EntityBCrudController is still being called EDIT action, but now the entity instance is not null anymore when doing $this->getContext()?->getEntity()->getInstance(), but it's even the wrong one -> EntityA instead of EntityB.

With version 4.26.5 everything works as expected. It started with 4.27.0