Error: Failed to fetch the data for an item [Exception... "Must have a non-null string spec or nsIFile o...

RESOLVED FIXED in Firefox 61

Status

()

defect
P1
normal
RESOLVED FIXED
Last year
Last year

People

(Reporter: standard8, Assigned: standard8)

Tracking

Trunk
Firefox 61
Points:
---

Firefox Tracking Flags

(firefox61 fixed)

Details

(Whiteboard: [nightly-js-sentry:3426153][fxsearch], )

Attachments

(1 attachment)

Assignee

Description

Last year
This bug was automatically filed from Sentry: https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3426153/

Error: Unexpected bookmark type
    at createItemInfoObject(undefined:1749:11)
    at next(undefined:1213:9)
    at promiseBookmarksTree(undefined:1834:24)
    at next(undefined:1213:9)
Assignee

Comment 1

Last year
According to the best info I can find, this error started on March 31st, I'm not sure what is actually causing it, so in the short term, I think we should add the type to the info, and maybe we can work out what is going on from there.

Comment 3

Last year
mozreview-review
Comment on attachment 8965299 [details]
Bug 1451719 - Add the failing type to a bookmarks error, and replace some xpcom interface usages with pure javascript ones.

https://reviewboard.mozilla.org/r/234036/#review239738

should we leave-open this one?
Attachment #8965299 - Flags: review?(mak77) → review+
Assignee

Comment 4

Last year
(In reply to Marco Bonardo [::mak] from comment #3)
> should we leave-open this one?

I debated that, and decided that due to how mozreview works, probably best let it close, and we can file a bug with the new error when it shows up.

Comment 5

Last year
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ef01b0080577
Add the failing type to a bookmarks error, and replace some xpcom interface usages with pure javascript ones. r=mak

Comment 6

Last year
bugherder
https://hg.mozilla.org/mozilla-central/rev/ef01b0080577
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → Firefox 61
You need to log in before you can comment on or make changes to this bug.