After the /e/ OS 22 upgrade magisk breaks boot.img after booting with it after additional setup.

[arch-user-france1]

Device: FP3
Android version: /e/ os (Android 10?)
Magisk version: newest default.

Image: images.ecloud.global/stable/FP3 IMG-e-22 (the only one ending with 6119-stable...) => boot.img

I flashed it like that:
fastboot flash boot_a boot-patched.img => nothing happened
fastboot flash boot_b boot-patched.img => /e/ recovery failed to boot into operating system and errors appear like:
failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: no such file or directory. Maybe this is because I wiped it by fastboot -w but the first time I didn't do this.

I tried to restore the boot.img but the same still happened
Might this be because the e.foundation uploaded a wrong/bad boot.img? I can boot after a factory reset but that's not what I want and I can manually boot too using fastboot boot boot.img.
Magisk version code: 24201

[arch-user-france1]

And manually booting the magisk image seems to be ok too.

[arch-user-france1]

Magisk seems to break after the additional setup. If I boot once more from the magisk img after the additional setup it's just ded.

[arch-user-france1]

#5553 idk if it's related.

[arch-user-france1]

#5555

[yujincheng08]

Duplicate of #5530