1129104 - [RTL][SMS] When user views message report, then returns to message thread the existing messages do not appear on screen

Status: VERIFIED DUPLICATE of bug 1121748

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

Description

[Brogan Zumwalt [Inactive]]

Attachment: Logcat

Description:
When user has language set to Arabic and enters a thread with at least one existing message in the SMS app, viewing message report, then returning to message thread causes the existing messages to not appear on screen. Exiting then re-entering thread resolves issue, but this will repeat any time user is returning to thread from a message report. 


Repro Steps:
1) Update a Flame to 20150203055641
2) Change language to Arabic
3) Launch messages app
4) Enter existing message thread
5) Long press any message and select "View message report"
6) Return to thread

Actual:
Existing messages not visible in thread after returning from viewing message report.

Expected:
Existing messages are still visible when returning to thread after viewing message report.

Environmental Variables:
Device: Flame 3.0
Build ID: 20150203055641
Gaia: ae5a1580da948c3b9f93528146b007fc4f6a712b
Gecko: ae5d04409cd9
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 38.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Repro frequency: 3/3, 100%
See attached: Youtube video clip & logcat
Youtube video link: http://youtu.be/_RZTQcjS5i4

Comment 1

[Brogan Zumwalt [Inactive]]

Issue does NOT occur on Flame 2.2

Existing messages are still visible when returning to thread after viewing message report.

Device: Flame 2.2
Build ID: 20150203002504
Gaia: cd62ff9fe199fb43920ba27bd5fdbc5c311016fc
Gecko: 11d93135c678
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 2

[KTucker [:KTucker][Inactive 3/4/2016]]

[Blocking Requested - why for this release]:

Nominating this 3.0? since all the messages will appear gone. Let's get a regression window here.

Comment 3

[KTucker [:KTucker][Inactive 3/4/2016]]

Bug 1079154 seems to be the cause for this issue.

Mozilla-inbound Regression Window

Last Working 
Environmental Variables:
Device: Flame 2.2
BuildID: 20150106230728
Gaia: 69ac77cfa938fae2763ac426a80ca6e5feb6ad25
Gecko: 13869ca774bb
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 37.0a1 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

First Broken 
Environmental Variables:
Device: Flame 2.2
BuildID: 20150106231227
Gaia: 69ac77cfa938fae2763ac426a80ca6e5feb6ad25
Gecko: 547a2d626a62
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 37.0a1 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Last Working gaia / First Broken gecko - Issue DOES occur
Gaia: 69ac77cfa938fae2763ac426a80ca6e5feb6ad25
Gecko: 547a2d626a62

First Broken gaia / Last Working gecko - Issue does NOT occur
Gaia: 69ac77cfa938fae2763ac426a80ca6e5feb6ad25
Gecko: 13869ca774bb

Gecko Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=13869ca774bb&tochange=547a2d626a62

Comment 4

[Peter Bylenga [:PBylenga]]

Simon can you take a look here?  Looks like this issue was introduced by the work on bug 1079154

Comment 5

[Simon Montagu :smontagu]

I don't yet have a FirefoxOS device and can't reproduce on desktop simulator (chiefly because I don't know how to do a "long press" there). Jonathan, can you test this?

Comment 6

[Julien Wajsberg [:julienw]]

Hey Simon, a longpress can be probably done with a right click.

Comment 7

[Julien Wajsberg [:julienw]]

I tried reproducing in latest Firefox Nightly (see [1] for step-by-step instructions) but this doesn't reproduce. Could be a B2G-only issue, maybe related to APZC ?

[1] https://github.com/julienw/gaia/blob/1082618-sms-readme/apps/sms/README.md#how-to-run-the-application-in-firefox + add "&& false" in the condition in l10n.js line 1656)

Comment 8

[Simon Montagu :smontagu]

(In reply to Julien Wajsberg [:julienw] from comment #6)
> Hey Simon, a longpress can be probably done with a right click.

That was the first thing I tried. (The second was Cmd+click, FWIW)

Comment 9

[Jonathan Kew [:jfkthame]]

I was able to reproduce this locally on a device. I'm currently rebuilding with patches for bug 1121748 to check whether that resolves the problem. Should have a result later this morning.

Comment 10

[Jonathan Kew [:jfkthame]]

Yes - AFAICT, bug 1121748 will fix this once its patches land.

Comment 11

[Julien Wajsberg [:julienw]]

Let's dupe then.

We can reopen if we still see this after bug 1121748 lands.

Thanks a lot!

Comment 12

[Peter Bylenga [:PBylenga]]

Adding qawanted to check if this bug reproduces after bug 1121748 lands.

Comment 13

[Coler]

This issue can't be repro on latest Flame 3.0 after bug 1121748 landing.
Reproduce rate:0/5
STRs:
1. Change language to Arabic
2. Launch messages app
3. Enter existing message thread
4. Long press any message and select "View message report"
5. Return to thread
**The thexisted message is still visible in thread. 
Attachment:Verify_RTL_SMS.mp4.

Flame 3.0 build:

Build ID               20150204162500
Gaia Revision          c2047a46e29696238e9b4c9caaba47736421449a
Gaia Date              2015-02-04 20:34:04
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/adfba0a07e9b
Gecko Version          37.0a2
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150204.195445
Firmware Date          Wed Feb  4 19:54:56 EST 2015
Bootloader             L1TC000118D0

Comment 14

[Coler]

Attachment: Verify_RTL_SMS.MP4

Comment 15

[Lancy(Leave from Mozilla)]

Per comment 13 and my own verification, the bug is fixed now and current issue never happens on Flame&N5 master build, so I mark it as “VERIFIED DUPLICATE”.

Device info:
Flame master build ID:20150722160203
N5 master build ID:20150722160203