Closed Bug 1116671 Opened 6 years ago Closed 4 years ago

[FFOS2.0][Woodduck][SMS]launch Messaging from contact won't change message unread status

Categories

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

defect

Tracking

(tracking-b2g:backlog, b2g-v2.0 wontfix, b2g-v2.0M wontfix, b2g-v2.1 affected, b2g-v2.1S affected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- wontfix
b2g-v2.0M --- wontfix
b2g-v2.1 --- affected
b2g-v2.1S --- affected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: sync-1, Unassigned)

References

Details

(Whiteboard: [sms-papercuts])

DEFECT DESCRIPTION:
 send a message from contact and stay on the screen, while receive a new message from this contact, the unread status won't change even User delete the new message. 
 And the notification keep on status bar till you read the message launch from Messaging directly or from status bar.
 
  REPRODUCING PROCEDURES:
 1.save a number to contacts, e.g. 10086;
 2.select the contact, touch the send message icon;
 3.type some characters, send it, and stay on this screen,wait for the reply SMS from this recepient;
 4.receive the SMS,you can read the SMS, but the notification keep on the status bar and won't disappear, you can even try to delete the new message with the notification no missing.->KO.
 
  EXPECTED BEHAVIOUR:
 no matter where you launch the Messaging APP from, should keep the new message status sync.
 
 ->0752-2611705(61405)
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:
I can reproduce this on woodduck. Gary, could you please take a look?

The problem in this bug is: new message notification will not disappear when user view incoming message on "Send Message" page invoked from Contact.
Blocks: Woodduck
Flags: needinfo?(gchen)
Seems a duplicate of bug 1105548, I will take a look.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1105548
I don't think this is a duplicate, but we'll be able to resolve using the same mechanism.
Component: Gaia → Gaia::SMS
Hi Chens,
   Per comment #3, Could you help to verify this issue again?
   Thanks.
Flags: needinfo?(gchen) → needinfo?(shchen)
The description may be different but I think these two bugs share the same root cause, both of them are lacking of some inter-instance communication mechanism. And as Julien said, we can use the same mechanism in bug 1105548 to fix it. I will follow up in bug 1105548 and provide PR for 2.0m
Flags: needinfo?(shchen)
Sherman, should we undupe here?
Flags: needinfo?(shchen)
Sure, let's undupe and I will pick up patch from bug 1105548
Status: RESOLVED → REOPENED
Flags: needinfo?(shchen)
Resolution: DUPLICATE → ---
Assignee: nobody → shchen
Status: REOPENED → ASSIGNED
blocking-b2g: --- → 2.0M?
See Also: → 1105548
blocking-b2g: 2.0M? → 2.0M+
This issue still WIP per bug 1105548. Will fix in m/c asap.
Status: ASSIGNED → NEW
blocking-b2g: 2.0M+ → 2.2?
tracking-b2g: --- → +
Depends on: 1105548
triage: similar to bug 1105548. non-blocking but please request for uplift once it's fixed.
blocking-b2g: 2.2? → backlog
Assignee: shchen → nobody
blocking-b2g: backlog → ---
[Tracking Requested - why for this release]:
Priority: P2 → P1
Whiteboard: [sms-papercuts]
Mass closing of Gaia::SMS bugs. End of an era :(
Status: NEW → RESOLVED
Closed: 6 years ago4 years ago
Resolution: --- → WONTFIX
Mass closing of Gaia::SMS bugs. End of an era :(
You need to log in before you can comment on or make changes to this bug.