opened 09:30PM - 21 Apr 23 UTC
issue: bug
severity: medium
status: confirmed
source: core:data-transfer
<!--
Hello 👋 Thank you for submitting an issue.
Before you start, please mak…e sure your issue is understandable and reproducible.
To make your issue readable make sure you use valid Markdown syntax.
https://guides.github.com/features/mastering-markdown/
Please ensure you have also read and understand the contributing guide.
https://github.com/strapi/strapi/blob/main/CONTRIBUTING.md#reporting-an-issue
-->
## 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
