1097884 - [Messages][Drafts] Thread List panel doesn't display "No messages" screen if invalid draft information is stored in IndexedDB

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[Oleg Zasypkin [:azasypkin]]

STR:

* Update device gaia with "gaia-reset" to clean all previous app data;
* Open Messages app and create _one_ draft;
* Enter to edit mode and remove the draft created above;
* Close Message app via Task Manager;
* Try to open and close (via Task Manager) Messages app several times;

Expected result: "No messages" string should be always displayed in Thread list;

Actual result: Sometimes you'll see just plain white screen.

The problems boils down to two things:

* Initially we have "{ 'draftIndex': null }" in IndexedDB, but once we created draft and removed it, we have "{ 'draftIndex': [[null,[]]] }" that makes the following statement true "Drafts.size === 1" + Drafts.forEach callback is never executed. That doesn't sound correct;

* There is a race between renderThreads and renderDrafts. So if renderThreads is completed before we get data about drafts from IndexedDB - we'll see "No messages" string, otherwise - we'll see plain white screen. The race is intermittent, that is why you need to run/close app several times to catch the error.

The same is true for v2.0 branch, BUT I can't catch this error there, either mozMobileMessage.getThreads is faster on v2.0, or we have pretty fast IndexedDB on master :)

Comment 1

[Julien Wajsberg [:julienw]]

Mass closing of Gaia::SMS bugs. End of an era :(

Comment 2

[Julien Wajsberg [:julienw]]

Mass closing of Gaia::SMS bugs. End of an era :(