Closed Bug 824552 Opened 12 years ago Closed 12 years ago

[SMS] After sent out the sms, it still shows that it's sending.

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

RESOLVED DUPLICATE of bug 822055
B2G C3 (12dec-1jan)
blocking-basecamp +

People

(Reporter: wachen, Assigned: kgrandon)

Details

Attachments

(1 file, 1 obsolete file)

*Phone: Unagi 2012-12-24 https://releases.mozilla.com/b2g/ *How to reproduce: 1. send an message to phone A 2. click on "<" to go back to sms list 3. go back in the message conversation with phone A *Expected Result: Not showing that sms is sending if phone A received its sms *Actual Result: Showing that sms is sending even if phone A received its sms
Attached image pic
blocking-basecamp: --- → ?
Please use pvtbuild for testing purposes
Triage: BB+, p3, c3 - user needs to understand if the message is sent or not. this causes confusion and user might resend the message again (incur unnecessary new sms charge)
blocking-basecamp: ? → +
Priority: -- → P3
Target Milestone: --- → B2G C3 (12dec-1jan)
I was talking a look, and think I have identified a fix. I also noticed that the same bug resulted in being unable to delete messages after re-visiting a thread, this will fix that too. Just noting in-case someone finds a dupe.
Assignee: nobody → kgrandon
Attached file Github pull request pointer (obsolete) —
This pull request fixes a few issues with the SMS app: 1 - Sending state when revisiting a thread. 2 - Multi-delete when revisiting a thread.
Attachment #695656 - Flags: review?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Attachment #695656 - Attachment is obsolete: true
Attachment #695656 - Flags: review?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: