876344 - Popup warning inconsistent when sending SMS in airplane mode

Status: RESOLVED WORKSFORME

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

Description

[Roy Collings]

User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31

Steps to reproduce:

Using Unagi with build: unagi-ICS.eng.master.Rel0.4.Sprint10.B-8.Gecko-f72a87a.Gaia-38ce006

1. Clear all threads.
2. Send SMS via contact - popup appears.
3. Send SMS via contact again - popup does not appear.
4. Clear all threads.
5. Come out of airplane mode.
6. Send SMS via contact (sends successfully).
7. Go into airplane mode.
8. Send SMS via same contact - popup does not appear.

Also ...
1. In airplane mode, send sms to a number which is not a contact - no popup.
2. send another sms to this contact - popup appears.


Actual results:

The popup warning does not always appear.


Expected results:

The popup warning should always appear (or at least be consistent). If you try to send sms to a number which is not a contact, you always get the warning.

Comment 1

[Jamie Charlton (:Jamie_)]

This has been taken care of in the current builds of 2.0 or higher. This is going to be closed as wont fix. If it starts happening again on a more current build feel free to open a new one.

Comment 2

[Julien Wajsberg [:julienw]]

Hey Charja, did you actually check on a build that this was working?

If yes, please close with WORKSFORME so that it's clear.
If no, please don't close the bug :D

Comment 3

[Jamie Charlton (:Jamie_)]

I had requested if someone in B2G with a device with service on it to check, A person in there verified that it was now working on a 2.0. I have marked this as such because I was instructed to deal with these as such, I was told to go from oldest filed bug and if I have the ability to check if they were working on a 2.0 or higher to mark them as wont fix due to the age and if I did not have the ability to check post a comment asking the reporter to check and see if was working on a current build, and that if there was no response within a week to mark as invalid. Below marking as invalid if found still occurring on a current build to report a new bug with updated information. I was instructed to do so by nhirata.

Comment 4

[Julien Wajsberg [:julienw]]

Thanks for the explanation, and thanks for doing this tedious work !

I think it's more appropriate to mark as WORKSFORME here (althought it's not really important, so don't worry).