[BUG] GetPropertiesAsync fails in Firefox with TypeError: e.body is null

[hectorm-bmg]

Library name and version

Azure.Storage.Blobs, Version=12.22.2.0

Describe the bug

From a Blazor Client side project, when I call the following:

var props = await blobClient.GetPropertiesAsync();

Firefox fails with the following error:
TypeError: e.body is null

Other browsers work as expected and I can see the properties for my blob.

Expected behavior

The properties for the blob are returned to be use as needed.

Actual behavior

In Firefox, an exception is generated with the error message :

TypeError: e.body is null

Reproduction Steps

• Create a SAS write uri for a new blob
• Get a SAS url for the blob
• Use the following method to upload the new blob from a blazor client side app running in Firefox. You'll notice that the call to GetPropertiesAsync will fail as described above.

'
public async Task UploadStream(string blobName, Stream stream, Uri sasTokenUri, long totalSize)
{
var containerClient = new BlobContainerClient(sasTokenUri);

var blobClient = containerClient.GetBlockBlobClient(blobName);

var blockIds = new List<string>();

var buffer = new byte[MaxChunkSize];
int bytesRead;
int blockNumber = 0;

var totalChunks = (totalSize / MaxChunkSize) + 1;

while ((bytesRead = await stream.ReadAsync(buffer, 0, buffer.Length)) > 0)
{
    Logger.LogInformation($"Uploading block {blockNumber}/{totalChunks} for {blobName}.");

    string blockId = Convert.ToBase64String(Encoding.UTF8.GetBytes($"{blockNumber:D6}"));
    blockIds.Add(blockId);

    // Upload the block
    using var chunkStream = new MemoryStream(buffer, 0, bytesRead);
    await blobClient.StageBlockAsync(blockId, chunkStream);

    blockNumber++;
}

// Commit the blocks
await blobClient.CommitBlockListAsync(blockIds);

var props = await blobClient.GetPropertiesAsync();

while (props != null && props.Value.ContentLength < totalSize)
{
    // Check that the file has finished uploading.
    await Task.Delay(5000);
    Console.WriteLine($"Waiting for blob {blobName} to finish uploading.");
    props = await blobClient.GetPropertiesAsync();
}

}
'

Environment

Blazor App running in an Azure App Service using .net 8.0
Version 8.0.405

Visual Studio 2022 17.12.3

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

[amnguye]

TypeError: e.body is null

looks like a JavaScript error.

Can you try doing a try-catch block around the GetPropertiesAsync call and get the exception stack trace that comes from that? If there's nothing that comes from that, I'm not sure if that's the source of error here.

[hectorm-bmg]

@amnguye, Thank you for looking into this!

Here's the exception I'm getting when executing GetPropertiesAsync:

fail: MyClient.Components.ProcessManager[0] Failed to Upload File: MyFile.txt System.Net.Http.HttpRequestException: TypeError: e.body is null ---> TypeError: e.body is null --- End of inner exception stack trace --- at System.Net.Http.BrowserHttpInterop.<CancelationHelper>d__131[[System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Net.Http.WasmHttpReadStream.g__Impl|2_0(WasmHttpReadStream self, Memory1 buffer, CancellationToken cancellationToken) at System.Net.Http.WasmHttpReadStream.ReadAsync(Memory1 buffer, CancellationToken cancellationToken)
at Azure.Core.Pipeline.ResponseBodyPolicy.CopyToAsync(Stream source, Stream destination, CancellationTokenSource cancellationTokenSource)
at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async) at Azure.Core.Pipeline.HttpPipelineSynchronousPolicy.InnerProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline)
at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async) at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async)
at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline, Boolean async) at Azure.Core.Pipeline.HttpPipelineSynchronousPolicy.InnerProcessAsync(HttpMessage message, ReadOnlyMemory1 pipeline)
at Azure.Core.HttpPipelineExtensions.ProcessMessageAsync(HttpPipeline pipeline, HttpMessage message, RequestContext requestContext, CancellationToken cancellationToken)
at Azure.Storage.Blobs.BlobRestClient.GetPropertiesAsync(String snapshot, String versionId, Nullable1 timeout, String leaseId, String encryptionKey, String encryptionKeySha256, String encryptionAlgorithm, String ifTags, RequestConditions requestConditions, RequestContext context) at Azure.Storage.Blobs.Specialized.BlobBaseClient.GetPropertiesInternal(BlobRequestConditions conditions, Boolean async, RequestContext context, String operationName) at Azure.Storage.Blobs.Specialized.BlobBaseClient.GetPropertiesAsync(BlobRequestConditions conditions, CancellationToken cancellationToken) ...

[amnguye]

Looking at the original findings that the GetProperties call works on different browsers, the other Blob API calls succeeding, and also looking at this stack trace, the Storage SDK may not be the source of this issue.

If you look at the System.Net.Http.WasmHttpReadStream.ReadAsync in the stack trace, this looks to be a Blazor used specific stream that's throwing this error.

This issue is better suited for the https://github.com/dotnet/aspnetcore/issues Repo that owns Blazor.

Apologies we can't assist further considering this is outside the scope of the Storage SDK.