Closed Bug 958738 Opened 10 years ago Closed 10 years ago

JavaScript error: app://sms.gaiamobile.org/js/message_manager.js, line 318: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMMozMobileMessageManager.getThreads]

Categories

(Firefox OS Graveyard :: RIL, defect)

x86_64
macOS
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v1.3 affected, b2g-v1.4 affected)

RESOLVED DUPLICATE of bug 952875
tracking-b2g backlog
Tracking Status
b2g-v1.3 --- affected
b2g-v1.4 --- affected

People

(Reporter: gkw, Assigned: airpingu)

References

Details

Attachments

(1 file)

Download:

http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/2014-01-10-00-40-09-mozilla-aurora/b2g-28.0a2.multi.mac64.dmg

Extract it and run using:

B2G.app/Contents/MacOS/b2g-bin -profile B2G.app/Contents/MacOS/gaia/profile/

Click Next all the way till Done until the FTU experience is over, then Skip the tutorial.

===

Launch the SMS app. You will hit:

JavaScript error: app://sms.gaiamobile.org/js/message_manager.js, line 318: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMMozMobileMessageManager.getThreads]
Could this be a dupe of bug 958943?

Gene, any idea of what's going on?
Component: Gaia::SMS → RIL
Flags: needinfo?(gene.lian)
Assignee: nobody → gene.lian
Flags: needinfo?(gene.lian)
It seems more likely that the fallback backend removed in bug#889898 that cause MobileMessageManager not able to access MobileMessageDatabaseService in b2g_desktop version.
Yeap! Thanks for the investigation. Sounds no issue.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Bevis, Gene, would we want to fail in a cleaner way?
This still happens with http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/2014/02/2014-02-06-04-02-03-mozilla-central/b2g-30.0a1.multi.mac64.dmg

It will be nice to have this fixed in B2G Desktop so that this error does not mask other errors.

Reopening. What is needed to move this forward?
Status: RESOLVED → REOPENED
Flags: needinfo?(gene.lian)
Resolution: WONTFIX → ---
FWIW, clicking on the compose button after launching the SMS app results in:

JavaScript error: app://sms.gaiamobile.org/js/thread_ui.js, line 961: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMMozMobileMessageManager.getSegmentInfoForText]

which I think might be related (or else we can file a new bug).
Put this bug into backlog.
blocking-b2g: --- → backlog
Attached patch PatchSplinter Review
Attachment #8406769 - Flags: feedback?(vyang)
Flags: needinfo?(gene.lian)
Depends on: 889898
(In reply to Gary Kwong [:gkw] [:nth10sd] from comment #6)
> Reopening. What is needed to move this forward?

Do you have a build config for b2g-desktop on Mac? mozconfig?
Flags: needinfo?(gary)
(In reply to Vicamo Yang [:vicamo][:vyang] from comment #10)
> Do you have a build config for b2g-desktop on Mac? mozconfig?

No, I have no idea. I used B2G Desktop builds that were available from tbpl.

http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/
Flags: needinfo?(gary)
Depends on: 952875
Blocks: 988711
Going to solve bug 952875 to prevent similar things from happening again.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
No longer depends on: 952875
Resolution: --- → DUPLICATE
Attachment #8406769 - Flags: feedback?(vyang)
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: