vich/uploader-bundle:1.21.1 - ReplacingFile does not create directory according to configured directory_namer - vichuploaderbundle

Question

Package
Version
vich/uploader-bundle
1.21.1
Symfony
5.4.19
PHP
7.4.30
I'am trying to use Vich\UploaderBundle\FileAbstraction\ReplacingFile (as described on https://github.com/dustin10/VichUploaderBundle/blob/1.21.1/docs/other_usages/replacing_file.md) to inject a file from the local file-system.
But the following ErrorException is thrown upon persisting the entity with the attached file:
ErrorException: Warning: copy(/var/www/var/storage/files/da/39/da39a3ee5e6b4b0d3255bfef95601890afd80709): failed to open stream: No such file or directory in /var/www/vendor/vich/uploader-bundle/src/Storage/FileSystemStorage.php on line 25
Call Stack:
0.0037 400328 1. {main}() /var/www/bin/console:0
0.0957 406696 2. require_once('/var/www/vendor/autoload_runtime.php') /var/www/bin/console:11
0.1202 4558088 3. Symfony\Component\Runtime\Runner\Symfony\ConsoleApplicationRunner->run() /var/www/vendor/autoload_runtime.php:35
0.1202 4558088 4. Symfony\Component\Console\Application->run(...
0.1224 4567696 5. Symfony\Bundle\FrameworkBundle\Console\Application->doRun(...
0.1781 15215392 6. Symfony\Component\Console\Application->doRun(...
0.2879 22494832 7. Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand(...
0.2879 22494832 8. Symfony\Component\Console\Application->doRunCommand(...
0.2933 22638600 9. Symfony\Component\Console\Command\Command->run(...
0.2935 22638600 10. App\Command\WatcherCommand->execute(...
5.9695 23904056 11. App\Service\FileHandler->handleEvent(...
12.2081 28132368 12. Doctrine\ORM\EntityManager->persist(...
12.2081 28132368 13. Doctrine\ORM\UnitOfWork->persist(...
12.2081 28132400 14. Doctrine\ORM\UnitOfWork->doPersist(...
12.2082 28132776 15. Doctrine\ORM\UnitOfWork->persistNew(...
12.2084 28133768 16. Doctrine\ORM\Event\ListenersInvoker->invoke($...
12.2084 28133768 17. Symfony\Bridge\Doctrine\ContainerAwareEventManager->dispatchEvent(...
12.2084 28133768 18. Vich\UploaderBundle\EventListener\Doctrine\UploadListener->prePersist(...
12.2089 28144592 19. Vich\UploaderBundle\Handler\UploadHandler->upload(...
12.2135 28407936 20. Vich\UploaderBundle\Storage\AbstractStorage->upload(...
12.2152 28439984 21. Vich\UploaderBundle\Storage\FileSystemStorage->doUpload(...
19.9282 28442848 22. copy($source_file = '/var/www/var/storage/symlinks/24410740-1466-45a9-be93-cbdbde4be40a/test6.txt', $destination_file = '/var/www/var/storage/files/da/39/da39a3ee5e6b4b0d3255bfef95601890afd80709') /var/www/vendor/vich/uploader-bundle/src/Storage/FileSystemStorage.php:25
19.9282 28444520 23. Symfony\Component\ErrorHandler\ErrorHandler->handleError(...
Link to Line in Question: https://github.com/dustin10/VichUploaderBundle/blob/1.21.1/src/Storage/FileSystemStorage.php#L25
It seams that the configured directory_namer in config/packages/vich_uploader.yaml did not do it's thing:
vich_uploader:
db_driver: orm
#mappings:
# products:
# uri_prefix: /images/products
# upload_destination: '%kernel.project_dir%/public/images/products'
# namer: Vich\UploaderBundle\Naming\SmartUniqueNamer
mappings:
file:
uri_prefix: null
upload_destination: '%app.storage.files_dir%'
namer:
service: App\Service\UploaderFileNamer
options: { property: 'checksum' }
directory_namer:
service: Vich\UploaderBundle\Naming\SubdirDirectoryNamer
options: { chars_per_dir: 2, dirs: 2 }
inject_on_load: true
This is my configured upload_destination:
❯ console debug:container --parameters | grep "files_dir"
app.storage.files_dir /var/www/var/storage/files
The ErrorException seams to be correct because the target-directory does not exist:
php#dev-64fb4d859b-btcv9:/var/www$ ls /var/www/var/storage/files/da/39
ls: cannot access '/var/www/var/storage/files/da/39': No such file or directory
^^ directory-namer 2nd level - does not exit ^^
php#dev-64fb4d859b-btcv9:/var/www$ ls /var/www/var/storage/files/da/
ls: cannot access '/var/www/var/storage/files/da/': No such file or directory
^^ directory-namer 1st level - does not exit ^^
php#dev-64fb4d859b-btcv9:/var/www$ ls /var/www/var/storage/files/
^^ configured upload-destination - exists ^^
Is that the expected behavior and do I need to trigger the directory_namer separately when using ReplacingFile? If so - how do can i accomplish that ?
In case it's a bug, is there some way to get the target path in advance so I can create the directory myself?
I was excepting that the ReplacingFile is handled like an UploadedFile and the directory_namer would create the target-directory according to the configuration.
I've tried using UploadedFile and it all worked as expected (the directory-namer did create the target-directory)