conflictStrategy: update fails
matt-jon35 opened this issue · 1 comments
When using the conflict strategy 'update' with the run mode 'dangerous' it returns the following errors:
WARN
A file with the same name already exists at location: /Home/Untitled folder/Test Doc.pdf. Updating the file contents.
ERROR
Action attachment.store caused an error: {}
Error
Error in action 'attachment.store': TypeError: fileData.blob.getBlob is not a function
Processing Trace:
"error": {
"message": "fileData.blob.getBlob is not a function",
"stack": "TypeError: fileData.blob.getBlob is not a function\n at DriveUtils.updateExistingFile (GmailProcessorLib:954:39)\n at DriveUtils.createFile (GmailProcessorLib:839:37)\n at GDriveAdapter.storeAttachment (GmailProcessorLib:981:33)\n at store (GmailProcessorLib:269:49)\n at descriptor.value (GmailProcessorLib:4275:35)\n at ActionRegistry.executeAction (GmailProcessorLib:221:20)\n at GmailProcessorLib:3633:60\n at Array.forEach ()\n at GmailProcessorLib:3630:18\n at Array.forEach ()"
}
The intended action given that the filename is identical is to update the file whilst retaining the original ID i.e. adding a version.
When running with the mode 'safe-mode' it correctly identifies that an identically named file name exists and does not do anything.
Thank you.
p.s. the playground for converting config is excellent!! Thank you.
🎉 This issue has been resolved in version 2.6.1 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀