Transfer feature hangs on asset transfer

[bolg55]

Bug report

Required System information

• Node.js version: 16+
• NPM version: 8+
• Strapi version: 4.9.2
• Is your project Javascript or Typescript: JS

Describe the bug

A clear and concise description of what the bug is.

Edit: Based on issue #16437 this does not seem to be limited to cloud.

When attempting to transfer from a local Strapi instance to a Strapi Cloud project, using:

yarn strapi transfer --to <url> --to-token <token>
or
npm run strapi transfer --to <url> --to-token <token>

The transfer hangs when it gets to the assets transfer. Only killing the process will stop it, which then produces an error.

Steps to reproduce the behavior

1. Go to a local Strapi project, running on 4.8+
2. Login to Strapi Cloud and ensure both local and cloud projects have same schema
3. Try to transfer from local to cloud using either:
   yarn strapi transfer --to <url> --to-token <token>
   or
   npm run strapi transfer --to<url> --to-token <token>
4. See error

Expected behavior

That the transfer would go through successfully.

Screenshots

[Boegie19]

@bolg55 issue seems also to be with --from from other hosts then strapi Cloud
#16437

[bolg55]

Updating name to reflect, thanks @Boegie19

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/transfer-operation-stuck/27705/2

[BorisKamp]

I can confirm I have the same problem, although it's from remote to local:

Im trying out the data transfer from my remote url (https://birdblocker-strapi.herokuapp.com/admin) to my local installation with npm run strapi transfer -- --from https://birdblocker-strapi.herokuapp.com/admin
After which I paste my transfer token which is of type full access with unlimited duration.

Both local and remote run Strapi 4.9.2

My console gets stuck at this:

boriskamp@MacBook-Pro-2 birdblocker-strapi % npm run strapi transfer -- --from https://birdblocker-strapi.herokuapp.com/admin

> birdblocker-strapi@0.1.0 strapi
> strapi

? Please enter your transfer token for the remote Strapi source [hidden]
? The transfer will delete all the local Strapi assets and its database. Are you sure you want to proceed? Yes
(node:36287) Warning: S3 configuration options passed at root level of the plugin's providerOptions is deprecated and will be removed in a future release. Please wrap them inside the 's3Options:{}' property.
(Use `node --trace-warnings ...` to show where the warning was created)

It's been there for 10 minutes now. Who has a clue what's wrong here? How can I debug this?

My remote logs show nothing out of the ordinary either

edit
I have tried this on multiple different instances. Different strapi instances, but also different VPS servers where they're hosted. All the same problem.

[nagman]

I have the same problem. I've tried to downgrade strapi to 4.9.0 (with which it worked at the time) on both my local and remote instances, and it still didn't work.
I wonder if it's related to the data in the database, because it should work when downgrading (I've kept the same database for the downgraded version).
I even tried a transfer between two computers of the same local network, and it still hangs after the Starting the compilation for TypeScript files in ... line.

For now, the solution I've found is to strapi export, copy the exported file to the destination server, and then strapi import, but it's much more time consuming than just strapi transfer.