Are you able to share the full stack trace of the error in the logs? Does the same happen if you pre-create the destination folder before installing the package? from the above it appears to relate to the import creating the folders to enable it to place content deeper in the tree. Can you check in...