Hello Social Plus Team,
I have encountered an issue with uploading videos using the amityco/ts-sdk. While uploads work correctly for smaller files or with higher Internet upload speeds, problems arise with larger files when the upload speed is lower.
For example, with an upload speed of 1.25 MB/s, I attempted to upload a 742 MB video file, which should take approximately 9 minutes. However, after about 4–5 minutes, the API returned a 500 or 502 error, and no valid response was received. In contrast, when a colleague with a 10 MB/s upload speed uploaded the same file, the process completed in roughly 1 minute without any issues. Based on these observations, it appears that the request may be timing out after around 4 minutes.
Could you please advise on how to resolve this issue? Would it be possible to increase the timeout value for such requests?
Hello @Radek, thank you for reaching out and sharing the information. We’ve forwarded your feedback to our team and will update you once we have more details.
Hi @Radek , no worries—we’ve already passed the images to the team. We won’t approve the post for public view as it contains your token and may include other sensitive information.
Hi @Radek, this is still in progress — we’re aiming to provide further updates/implement a solution by early next week. We will keep you posted on the update, thank you for your patience.
Hello @Radek, good news! Our team has increased the server-side timeout limit, which should now allow for smoother handling of large file uploads on slower connections. With this update, you should be able to upload successfully.
However, for the best experience, we recommend using an internet speed of around 5–20 MB/s, as this will greatly improve upload performance.
Hello @Radek, it seems the solution we applied wasn’t sufficient. We’re now working on implementing it in the SDK as well, with the aim of releasing the fix in the upcoming sprint. We’ll let you know once it’s released.
Hello @Radek , For the issue you reported, our team has already addressed and resolved it.
Please try updating to TS SDK version v7.2.0 and recheck on your side.
Let us know if the issue persists or if you need any further assistance.
Hello @Radek , Thank you for sharing the update. We understand that increasing the timeout has helped slightly, but hasn’t fully resolved the issue on your end.
To help us investigate further and find the best possible solution, could you kindly share:
The steps to reproduce the issue
Any error logs you’re seeing
A screen recording or screenshot of the behavior
We truly appreciate your patience and cooperation, and we’ll do our best to support you through this.
