Bug - LargeFileUploadTask will not report 100% upload progress

[ChikyChan]

Bug Report

Prerequisites

• Can you reproduce the problem?
• Are you running the latest version?
• Are you reporting to the correct repository?
• Did you perform a cursory search?

For more information, see the CONTRIBUTING guide.

Description

[Description of the bug or feature]

I was following the Upload large files using the Microsoft Graph SDKs sample to implement file upload function, and when I use this implemented function to file upload, I found that the uploadEventHandlers.progress will not be triggered while the last slice uploaded.

I checked the source code, found that if the last slice uploaded, Graph API will respond the driveItem information with 201 Created status code, and in source code, if Graph API return 201, it will return the response immediately.

Console Errors: None

Screenshots: [If applicable, add screenshots to help explain your problem]
The network requests

LargeFileUplaodTask source code
LargeFileUploadTask.ts

Steps to Reproduce

1. Follow the steps Upload large files using the Microsoft Graph SDKs
2. Login my application and proceed file upload.

Expected behavior:
LargeFileUploadTask report 100% after file upload finished

Actual behavior:
LargeFileUploadTask will not report 100% after file upload finished, like dotnet client did.

Additional Context

Add any other context about the problem here..

Usage Information

Request ID - Value of the requestId field if you are receiving a Graph API error response
None

SDK Version - [SDK version you are using] 3.0.2

• Node (Check, if using Node version of SDK)

Node Version - [The version of Node you are using]

• Browser (Check, if using Browser version of SDK)

Browser Name - [The name of Browser that you are using for SDK]
Edge

Version - [The version of the browser you are using]
Version 104.0.1293.47 (Official build) (64-bit)

[rkodev]

Hi @ChikyChan thanks for reporting this.

This issue is currently being looked at and will be updated accordingly when fixed.

[nikithauc]

Fix released in 3.0.3