Description
When downloading two documents that have identical content (same name, size, and bytes) but different remote file IDs, the second file never receives an updateFile with is_downloading_completed=true. However, calling getFile shows the file is actually downloaded.
Steps to reproduce
- Have two messages with documents that have identical content but were uploaded separately (different remote.unique_id)
- Call
downloadFile for the first document → works correctly, receive updateFile with is_downloading_completed=true
- Call
downloadFile for the second document → never receive updateFile with is_downloading_completed=true
- Call getFile for the second document → shows is_downloading_completed=true
Example
First file (works correctly):
updateFile: file_id=100, is_downloading_completed=true, remote.unique_id="AAA111"
Second file (broken):
updateFile: file_id=200, is_downloading_active=true, is_downloading_completed=false, remote.unique_id="BBB222"
// No further updateFile received
getFile(200): is_downloading_completed=true, remote.unique_id="AAA111" // Note: unique_id changed after merge
Description
When downloading two documents that have identical content (same name, size, and bytes) but different remote file IDs, the second file never receives an updateFile with is_downloading_completed=true. However, calling getFile shows the file is actually downloaded.
Steps to reproduce
downloadFilefor the first document → works correctly, receiveupdateFilewithis_downloading_completed=truedownloadFilefor the second document → never receiveupdateFilewithis_downloading_completed=trueExample
First file (works correctly):
Second file (broken):