897432 - [Buri][FOTA][SMS]The message list disappear when enter the Message

Status: RESOLVED DUPLICATE of bug 887701

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

Description

[sync-1]

Created an attachment (id=468327)
 0724
 
 DEFECT DESCRIPTION:
 The message list disappear when enter the Message
 
 REPRODUCING PROCEDURES:
 Precondition:
 Have some messages before upgrading
 
 1.Upgrade from FFOS V1.0.1 to FFOS V1.1 by fota.
 2.Download diff package,and install it,it will upgrade succeed.
 3.Then click the Message,find the message list disappear. --KO
 
 
 EXPECTED BEHAVIOUR:
 The message list can't disappear when enter the Message
 
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 Critical
 
 REPRODUCING RATE:
 5/5
 
 For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Clone from brother

Comment 2

[sync-1]

Attachment: 493681-adblog

Comment 3

[sync-1]

Clone from brother

Comment 4

[Alex Keybl [:akeybl]]

Can you explain step 2? Is that an OTA update after a FOTA?

Comment 5

[田旻]

(In reply to Alex Keybl [:akeybl] from comment #4)
> Can you explain step 2? Is that an OTA update after a FOTA?

No, we didn't use a OTA to update, we just use a FOTA to update.

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Can we repro this on our side with just an OTA?

Comment 7

[Natalya Kot [:nkot]]

Have tested on Unagi, the issue did not reproduce

1. manually flashed to 20130728070232 v1.0.1 build
2. pushed the updates.js which was modified to look at the 1.1.0/nightly update channel
3. sent a few SMS to a test device, back and forth
4. performed OTA
 ==> successfully updated to 20130729070226 v1.1 build
 ==> all messages are kept, no data loss

Comment 8

[Alex Keybl [:akeybl]]

tianm - can you help clarify how your STR differ from those in Comment 7? It appears we are not able to reproduce on our end.

Comment 9

[田旻]

(In reply to Alex Keybl [:akeybl] from comment #8)
> tianm - can you help clarify how your STR differ from those in Comment 7? It
> appears we are not able to reproduce on our end.

When we update from version 1.0 to version 1.1, sms indexBD database don't update automatically.
From the log in the attachment we can see:

E/GeckoConsole(  140): [JavaScript Error: "[Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMobileMessageService.createThread]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseService.js :: onsuccess :: line 2295"  data: no]" {file: "jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseServic.js" line: 2295}]

Comment 10

[田旻]

From the logs above analysis, I doubt the parameters in the function creatThread is illegal, as follow, which means the database didn't update correctly. 

gMobileMessageService.createThread(threadRecord.id,
                                           threadRecord.participantAddresses,
                                           threadRecord.lastTimestamp,
                                           threadRecord.subject,
                                           threadRecord.unreadCount,
                                           threadRecord.lastMessageType);

On the other hand, how OTA trigger an update in sms database? I want to compare the difference.

Comment 11

[bhavana bajaj [:bajaj]]

needsinfo gene, anything obvious given the GECKO error in comment #9 ?

Comment 12

[Askeing Yen[:askeing][:fyen]]

(In reply to 田旻 from comment #9)
> (In reply to Alex Keybl [:akeybl] from comment #8)
> > tianm - can you help clarify how your STR differ from those in Comment 7? It
> > appears we are not able to reproduce on our end.
> 
> When we update from version 1.0 to version 1.1, sms indexBD database don't
> update automatically.
> From the log in the attachment we can see:
> 
> E/GeckoConsole(  140): [JavaScript Error: "[Exception... "Component returned
> failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE)
> [nsIMobileMessageService.createThread]"  nsresult: "0x80070057
> (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
> jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseService.js
> :: onsuccess :: line 2295"  data: no]" {file:
> "jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseServic.js"
> line: 2295}]
The error message is the same with Bug 887701 (see https://bugzilla.mozilla.org/show_bug.cgi?id=887701#c4 ).
It looks like the duplicate.

Tianm, Could you please provide your v1.1.0 gaia info? Or test with new v1.1.0 gaia code.

Comment 13

[Gene Lian (I already quit Mozilla)]

(In reply to 田旻 from comment #9)
> (In reply to Alex Keybl [:akeybl] from comment #8)
> > tianm - can you help clarify how your STR differ from those in Comment 7? It
> > appears we are not able to reproduce on our end.
> 
> When we update from version 1.0 to version 1.1, sms indexBD database don't
> update automatically.
> From the log in the attachment we can see:
> 
> E/GeckoConsole(  140): [JavaScript Error: "[Exception... "Component returned
> failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE)
> [nsIMobileMessageService.createThread]"  nsresult: "0x80070057
> (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
> jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseService.js
> :: onsuccess :: line 2295"  data: no]" {file:
> "jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseServic.js"
> line: 2295}]

This kind of issue often happens when the MobileMessageThread::Create(...) (in MobileMessageThread.cpp) is eating bad parameters.

Hi Alexandre, are you available to look into this issue again? since you used to solve exactly the similar issue. Per comment #12, we're doubting this issue is already solved.

Comment 14

[:gerard-majax]

(In reply to Gene Lian [:gene] from comment #13)
> (In reply to 田旻 from comment #9)
> > (In reply to Alex Keybl [:akeybl] from comment #8)
> > > tianm - can you help clarify how your STR differ from those in Comment 7? It
> > > appears we are not able to reproduce on our end.
> > 
> > When we update from version 1.0 to version 1.1, sms indexBD database don't
> > update automatically.
> > From the log in the attachment we can see:
> > 
> > E/GeckoConsole(  140): [JavaScript Error: "[Exception... "Component returned
> > failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE)
> > [nsIMobileMessageService.createThread]"  nsresult: "0x80070057
> > (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
> > jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseService.js
> > :: onsuccess :: line 2295"  data: no]" {file:
> > "jar:file:///system/b2g/omni.ja!/components/MobileMessageDatabaseServic.js"
> > line: 2295}]
> 
> This kind of issue often happens when the MobileMessageThread::Create(...)
> (in MobileMessageThread.cpp) is eating bad parameters.
> 
> Hi Alexandre, are you available to look into this issue again? since you
> used to solve exactly the similar issue. Per comment #12, we're doubting
> this issue is already solved.

It looks very very similar to the bogus update that I fixed ... I won't be able to have a look into this before next Monday, though.

Comment 15

[Gene Lian (I already quit Mozilla)]

No worries! Alexandre.

Hi Tianm, could you please check this issue again with the patch included at Bug 887701? I think this issue should have been solved.

Comment 16

[Lukas Blakk [:lsblakk] use ?needinfo]

Minusing here, bug 887701 is fixed and might have resolved this issue.  Renominate if it can still be reproduced.

Comment 17

[田旻]

(In reply to Gene Lian [:gene] from comment #15)
> No worries! Alexandre.
> 
> Hi Tianm, could you please check this issue again with the patch included at
> Bug 887701? I think this issue should have been solved.

OK, I will give you the results soon.

Comment 18

[田旻]

(In reply to Gene Lian [:gene] from comment #15)
> No worries! Alexandre.
> 
> Hi Tianm, could you please check this issue again with the patch included at
> Bug 887701? I think this issue should have been solved.

Thanks a lot. SMS database can be updated correctly, and this problem has been fixed.

Comment 19

[Askeing Yen[:askeing][:fyen]]

Base on c15, mark as dup of 887701 and close it.

Comment 20

[Askeing Yen[:askeing][:fyen]]

(In reply to Askeing Yen[:askeing] from comment #19)
> Base on c15, mark as dup of 887701 and close it.
> 
> *** This bug has been marked as a duplicate of bug 887701 ***
s/c15/c 18/g