aws-android-sdk-s3 database : it is found that the database table has not been cleared after the multipart upload is completed

[Devin12355]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.

Language and Async Model

Java

Amplify Categories

Storage

Gradle script dependencies

Details

// Put output below this line

Environment information

Details

# Put output below this line
 
Gradle 8.9

Please include any relevant guides or documentation you're referencing

No response

Describe the bug

From the database awss3transfertable.db, it is seen that main_upload_id has not been cleared after upload finish

Reproduction steps (if applicable)

No response

Code Snippet

// Put your code below this line.

Log output

Details

// Put your logs below this line

Configuration File

No response

GraphQL Schema

Details

// Put your schema below this line

Additional information and screenshots

No response

[mattcreaser]

Hi @Devin12355, do you see your listener being called with TransferState.COMPLETED? Any additional details you could provide would help narrow this issue down.

[Devin12355]

hi @mattcreaser
aws-android-sdk-s3 version:2.81.0

During the transfer process, I saw that files larger than 5M were sliced into multiple segments for uploading, and the database is as follows:
https://raw.githubusercontent.com/Devin12355/pic-cache/main/aws4.jpeg

​ after finish upload file with TransferUtility.upload I have receive the TransferState.COMPLETED message from this callback TransferListener.onStateChanged,I saw that "_id" is "1" has already delete but main_uoload_id is "1" not delete ,the database as follows:
https://raw.githubusercontent.com/Devin12355/pic-cache/main/aws3.jpeg

database may keep growing larger if the database is not cleaned, I'm not sure if there is a corresponding interface to clean it.

//java/com/amazonaws/mobileconnectors/s3/transferutility/TransferDBBase.java
 public int delete(Uri uri, String selection, String[] selectionArgs) {
      final int uriType = uriMatcher.match(uri);
      int rowsDeleted = 0;
      ensureDatabaseOpen();
      switch (uriType) {
          case TRANSFERS:
              rowsDeleted = database.delete(TransferTable.TABLE_TRANSFER, selection,selectionArgs);
              break;
          case TRANSFER_ID:
              final String id = uri.getLastPathSegment();
              if (TextUtils.isEmpty(selection)) {
                   rowsDeleted = database.delete(TransferTable.TABLE_TRANSFER, TransferTable.COLUMN_ID + "=" + id, null);
              } else {
                  rowsDeleted = database.delete(TransferTable.TABLE_TRANSFER, TransferTable.COLUMN_ID + "="+ id + " and " + selection, selectionArgs);
              }
              //add by devin 2025-10-09
              //database.delete(TransferTable.TABLE_TRANSFER,TransferTable.COLUMN_MAIN_UPLOAD_ID + "=" + id, null);
              break;
          default:
                throw new IllegalArgumentException("Unknown URI: " + uri);
      }
     return rowsDeleted;
 }

is it possible to delete the same "main_uoload_id" when deleting the database field TRANSFER_ID from the source code ?

[mattcreaser]

Thank you for the detailed description @Devin12355. Let me look into this issue and get back to you.

[Devin12355]

Ok, looking forward to reply @mattcreaser