nsIMsgCopyService.CopyMessages and nsIMsgFolder.deleteMessages fail with recent trunk builds

RESOLVED INVALID

Status

MailNews Core
Backend
--
major
RESOLVED INVALID
10 years ago
10 years ago

People

(Reporter: Eyal Rozenberg, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

46.95 KB, application/x-xpinstall
Details
(Reporter)

Description

10 years ago
Created attachment 338721 [details]
removedupes 0.3.1

I'm using nsIMsgCopyService.CopyMessages to move messages from a source folder to the trash. Same code used to work on earlier SM trunk builds and works on TB 2.0.0.x . All arguments seem to be in order... still, I'm getting:

Error: Could not convert JavaScript argument arg 1 [nsIMsgCopyService.CopyMessages] = NS_ERROR_XPC_BAD_CONVERT_JS
Source file: chrome://removedupes/content/removedupes-common.js
Line: 332

(attaching my extension's build so you could trigger this too; use it on a folder with some dupes and try removing them.)
(Reporter)

Updated

10 years ago
Summary: nsIMsgCopyService.CopyMessages → nsIMsgCopyService.CopyMessages fails with recent trunk builds
(Reporter)

Comment 1

10 years ago
Seeing the same thing with 

Error: Could not convert JavaScript argument arg 0 [nsIMsgFolder.deleteMessages] = NS_ERROR_XPC_BAD_CONVERT_JS
Source file: chrome://removedupes/content/removedupes-common.js
Line: 309
Summary: nsIMsgCopyService.CopyMessages fails with recent trunk builds → nsIMsgCopyService.CopyMessages and nsIMsgFolder.deleteMessages fail with recent trunk builds
Bug 435290 changed the second argument of CopyMessages from nsISupportsArray to nsIArray; CopyFolders in that interface also changed.

nsIMsgFolder::deleteMessages has also changed in a similar fashion.

Therefore you need to update your extension.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.