[BUG] Deserializing AcsEmailDeliveryReportReceivedEventData data from EventGridEvent does not populate DeliveryAttemptTimestamp property about azure-sdk-for-net HOT 11 CLOSED

Thank you for your feedback. Tagging and routing to the team member best able to assist.

from azure-sdk-for-net.

I haven't been able to reproduce this bug. Would it be possible for you to include a zipped minimal repro project that I can run?

from azure-sdk-for-net.

Hi @markduregon. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

from azure-sdk-for-net.

This is the Windows Service that is using the code above and is experiencing the issue. Hope you are able to get what you need from this to be able to replicate the issue. IMHO I though it might be related to encoding of the timestamp data, whether that is done by ACS putting the message onto the queue, or getting the messge off the queue, I am not sure. But library doesn't appear to be able to handle it either way. I also debugged and tried removing the weird encoding and replacing with a format you would expect and same result. Hence the bug report.

from azure-sdk-for-net.

I'm not really sure what to look at. I was hoping for a simple console app that includes the payload and the code to deserialize the payload.

from azure-sdk-for-net.

Hi @markduregon. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

from azure-sdk-for-net.

AcsEventDemo.zip
OK this is as simple as I could make it.

from azure-sdk-for-net.

Additionally, similar behaviour is also experienced when processing AcsEmailEngagementTrackingReportReceivedEventData events and the UserActionTimestamp is also null.

from azure-sdk-for-net.

The issue is that the deserialization is expecting "deliveryAttemptTimeStamp" as the property name, as opposed to "deliveryAttemptTimestamp" (note the lower case s) as in your sample. Is the live service returning a lower case s?

from azure-sdk-for-net.

Yes. As stated in the code example I sent you, the JSON in that is copied from an real event from the message queue. Can see you have created a PR to fix this. What would be the timeframe of a new package being available for a breaking change release?

from azure-sdk-for-net.

We are planning to ship a new version next week. Note this is not a breaking change, but rather a bug fix to deserialize the events correctly.

from azure-sdk-for-net.