'Object reference not set to an instance of an object' while migrating attachment

[IzzieGFR]

Hello,

I am facing an issue as I am testing the migration of work items, including attachment.

Here's the log part where I get the error (full log & config files attached)
logs-attachment-issues.txt
configuration-fileissue.json:

[09:10:11 INF] [v15.0.3] AttachmentMigrationEnricher: Migrating 6 attachemnts from 47215 to 79160
[09:10:11 DBG] [v15.0.3] REPGI0003_574_test period.zip
[09:10:11 DBG] [v15.0.3] ...downloading REPGI0003_574_test period.zip to c:\temp\WorkItemAttachmentExport\47215
[09:10:11 ERR] [v15.0.3] Exception downloading attachements
System.NullReferenceException: La référence d'objet n'est pas définie à une instance d'un objet.
à MigrationTools.ProcessorEnrichers.TfsAttachmentEnricher.ExportAttachment(WorkItem wi, Attachment wia, String exportpath) dans D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\ProcessorEnrichers\TfsAttachmentEnricher.cs:ligne 119
[09:10:11 DBG] [v15.0.3] AttachmentMigrationEnricher: Exported null to disk

The error is mentionned in French but it's "Object reference not set to an instance of an object"

When I look into the temp files, the folder is created but is empty.

Not sure what to do next so I would be very grateful to get some help.

Thanks a lot!

[MrHinsh]

We have a fix coming throug for this #2008

[MrHinsh]

It will be in preview pretty soon.

[shankar-krishnan-serv]

do we have an update on this. I am having the same issue and i am on the latest package

[MrHinsh]

@IzzieGFR, @shankarkrishnanReya this is not a breaking issue. It should continue to process attachments.

This could be an issue with this specific attachment, and can either be ignored, or you can debug in visual studio and see why this attachment has an issue.

[IzzieGFR]

I wasn't working with any kind of attachment until I updated to version 19.0.4. Now it works for me 🎉
Thank you @MrHinsh & team!