Closed
Bug 885253
Opened 13 years ago
Closed 13 years ago
[SMS/MMS] Send message option is not responding after it has been used previously
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(blocking-b2g:leo+)
RESOLVED
DUPLICATE
of bug 880115
| blocking-b2g | leo+ |
People
(Reporter: isabelrios, Assigned: johnhu)
Details
(Whiteboard: MMS_TEF)
Unagi device, build:
Gecko-856e202
Gaia-aea6834
PROCEDURE
There should be at least a message thread with a contact
1. Open the message thread
2. Tap on the header
3. Tap on Send message option
4. Go back to previous menu
5. Then tap on the header again and on Send option
6. Go to another thread and repeat from step 2.
EXPECTED
The option is always available and works fine
ACTUAL
After going back once pressed Send message option, next time trying to use that option (in the same or another thread) nothing happens. It stops working
| Assignee | ||
Updated•13 years ago
|
Assignee: nobody → johu
Updated•13 years ago
|
blocking-b2g: leo? → leo+
| Assignee | ||
Comment 1•13 years ago
|
||
After investigation, this bug looks similar to bug 880115. There is a lock for preventing double entrance to send activity of SMS when first one is processing. In bug 880115, it says a way to make it never unlock.
If we tap header to create send message, this is the first send activity issued. Go back and tap header again, this is the second send activity issued. And according bug 880115, the second one is canceled because of the lock.
I think this one is a duplicate of bug 880115, the main cause is the same and can use the same patch. I had tried the patch of bug 880115 and found this bug disappeared.
Isabel, can you confirm that?? If yes, let us mark this as a duplicate.
Flags: needinfo?(isabelrios)
| Assignee | ||
Comment 2•13 years ago
|
||
Isabel,
A week pasted. I marked it as duplicate. If you feel it is wrong, please reopen it.
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: needinfo?(isabelrios)
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 3•13 years ago
|
||
Hi John,
I cannot reproduce this problem anymore. Thanks
You need to log in
before you can comment on or make changes to this bug.
Description
•