Strapi loses the Admin Menu and Auth logo on transfer

[chintal]

Bug report

Required System information

• Node.js version: lts/iron (v20.12.2)
• NPM version: v10.5.0
• Strapi version: 4.20
• Database: postgres
• Operating system: linux / debian
• Is your project Javascript or Typescript: TypeScript

Describe the bug

Using npm run strapi transfer to=... causes the remote Strapi to lose any configured custom logo for the Admin menu and Auth. I also noticed this behaviour earlier today when I used strapi export and then strapi import to migrate from sqllite to posgtres. I put it down at the time to some difference between sqllite and postgres. However, the same behaviour occured on the transfer between two postgres backed strapi instances as well.

Steps to reproduce the behavior

1. Install strapi on a remote, and get the transfer token.
2. Also set a custom Menu logo and Auth logo
3. Do exactly the same with a local strapi instance. I'm unsure if you need to have a custom logo on the source strapi to trigger this behaviour. I have always had a custom logo when I've noticed it.
4. Use npm run strapi transfer to=.. from the local strapi to the freshly created remote with a custom logo.

Expected behavior

I expect one of the two to happen :

• The to target gets the logo from the from source.
• The to target retains whatever logo was originally configured on it, making its behaviour similar to what happens with admin accounts.

What actually happens

The to target loses the logo. It does not seem to revert to the default logo, instead showing the empty box of a missing image src.

Additional context

This is something of a pain when it comes to moving data around. It isn't a serious issue as such, I'm sure we can live with the Strapi logo and avoid the problem entirely. That said, I would still characterise this as a rather annoying quality of life bug.