BlobStorage is not tracking changes in state causing outdated state to be saved

[MathieuMarchant]

Version

4.19.1

Describe the bug

Looking at the documentation and samples, the way to update state is:

• to create a property accessor from the state
• fetch object from state with this accessor
• update properties of the object
• save changes on the state

Example code in the StateManagementBot

When doing so with MemoryStorage, everything works as expected.

When using Blob Storage, the initial state is written to the storage.
However when retrieving the object and updating it, on SaveChangesAsync the updated object is not correctly written.
Even when using the force:true the state is updated, but with the original version of the object, instead of the updated object.

To Reproduce

Steps to reproduce the behavior:

1. Configure in Startup your storage to use blob storage services.AddSingleton<IStorage>(new BlobsStorage(dataConnectionString, "bot-state"));
2. Configure an object to use as state e.g. "ConversationState" services.AddSingleton<ConversationState>();
3. OnTurnAsync create property and retrieve conversation state

var conversationDataAccessor = _conversationState.CreateProperty<ConversationData>(nameof(ConversationData));
var conversationData = await conversationDataAccessor.GetAsync(turnContext, () => new ConversationData(), cancellationToken);

4. Update conversationData and save changes

conversationData.Step = "Feedback";
conversationData.StepUpdated = DateTime.Now;
await _conversationState.SaveChangesAsync(turnContext, true, cancellationToken);

5. On next turn, update the conversationData.Step and save changes again.

conversationData.Step = "LastStep";
conversationData.StepUpdated = DateTime.Now;
await _conversationState.SaveChangesAsync(turnContext, true, cancellationToken);

6. Validate the state object in the blob container using the conversation ID
7. Step will still be "Feedback"

Expected behavior

State in blob container should reflect changes done to the object, holding "LastStep".

Additional context

While using the force parameter, doesn't solve the issue. Using SetAsync does provide a workaround
await conversationDataAccessor.SetAsync(turnContext, conversationData, cancellationToken);

[ErwanL08]

I have the same issue since i update the package from 4.18.1 to 4.19.1 :(

[anishprasad01]

Thank you for your report.

This is a known issue that was identified recently. We will be addressing this as soon as possible. Please refrain from updating Microsoft.Bot.Builder.Azure packages to 4.19.0 or 4.19.1 until the issue is resolved.