-
Notifications
You must be signed in to change notification settings - Fork 123
Open
Description
[V2.2.0] Upload Cleanup Fails to Delete File After Successful Upload, Leading to Inconsistent State
Description
In version 2.2.0, after an upload completes successfully, the cleanup process fails to delete the uploaded file from the system due to an unknown reason I faced. As a result:
- The uploaded file remains in the storage.
- The upload object is removed from
currentUploads
. - If a
createOrResume
is called later, the file will be detected as existing, butearlierUpload == nil
. The upload status becomesnil
, reaching an unhandled state, leading to this upload task permanently hanging no matter how many times it is retried.
Steps to Reproduce
- Start an upload using TUSKit.
- Let the upload complete successfully.
- Observe that during cleanup, force trigger an error when deleting the file to simulate the case.
- The upload entry is removed from
currentUploads
, but the file remains. - Retry the same upload; the system reaches an unhandled state.
Expected Behavior
- After a successful upload, the cleanup process should correctly remove the uploaded file.
- The upload state should remain consistent to avoid unexpected behavior on retries.
Environment
- TUSKit Version: 2.2.0
- Platform: iOS / macOS
Additional Context
I understand that v2.2.0 is a legacy version, and upgrading is not a quick or easy option for me due to system stability concerns. Logging this issue here first as documentation, while I plan to fork my own version for a fix.
Metadata
Metadata
Assignees
Labels
No labels