Closed Bug 1029474 Opened 10 years ago Closed 7 years ago

An error sending an SMS MO should reset the verification flow

Categories

(Core :: DOM: Device Interfaces, defect)

Product:
Core
Component:
DOM: Device Interfaces
Platform:
All
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: ferjm, Unassigned)

References

Details

(Keywords: feature)

After a failing sending an SMS within the SMS MO flow we are not notifying about this error and the user needs to wait for the timeout to be able to retrigger the verification flow. Gecko I 1403608926744 MobileId DEBUG Creating verification code timer Gecko I 1403608926747 MobileId DEBUG Observing messages from Mozilla@ Gecko I 1403608926763 MobileId DEBUG Sending /sms/momt/verify 73f730932c888a58b8a4a356b27b4e7d75f6cbc094c33e94a38be953ced8e6d4 to +34xxxxxxx GeckoConsole E UTM:SVC TimerManager:notify - notified @mozilla.org/b2g/webapps-update-timer;1 Gecko I 1403608927961 MobileId ERROR Error sending silent message 3 Gecko I 1403608927965 MobileId WARN doVerification 3 We should notify about this error and probably ask the user for her number as the SMS MO+MT flow will likely fail again.
Whiteboard: ft:loop
Maria -- Will someone from your team own this bug or should I find a bug owner? Thanks.
Flags: needinfo?(oteo)
After talking with Fernando we have agreed that this bug is not a blocker, it's for improving the user experience and due to the time constraints we should leave it for 2.1 version.
Assignee: nobody → ferjmoreno
feature-b2g: --- → 2.1
Flags: needinfo?(oteo)
As I am only working on blockers right now I'm resetting the assignee just in case someone else want's to take it :)
Assignee: ferjmoreno → nobody
Removing "ft:loop" from the whiteboard. Thank you, Maria and Fernando.
Whiteboard: ft:loop
(In reply to Maria Angeles Oteo (:oteo) PTO 4th-25th Aug from comment #2) > After talking with Fernando we have agreed that this bug is not a blocker, > it's for improving the user experience and due to the time constraints we > should leave it for 2.1 version. Hi, Maria, because we don't have an owner on this bug, and the feature landing date is coming(9/2), do you expect to land this before that? I suggest to postpone this to 2.2. What do you think? Thank you.
feature-b2g: 2.1 → 2.2
Flags: needinfo?(oteo)
Use feature-b2g:2.2? rather than just 2.2.
feature-b2g: 2.2 → 2.2?
(In reply to Kevin Hu [:khu] from comment #5) > (In reply to Maria Angeles Oteo (:oteo) PTO 4th-25th Aug from comment #2) > > After talking with Fernando we have agreed that this bug is not a blocker, > > it's for improving the user experience and due to the time constraints we > > should leave it for 2.1 version. > > Hi, Maria, because we don't have an owner on this bug, and the feature > landing date is coming(9/2), do you expect to land this before that? I > suggest to postpone this to 2.2. What do you think? > > Thank you. Completely agree Thanks Kevin!
Flags: needinfo?(oteo)
Wilfred, are you on top of it? Thanks.
feature-b2g: 2.2? → ---
Flags: needinfo?(wmathanaraj)
Flags: needinfo?(wmathanaraj)
Keywords: feature
Cleaning up Device Interfaces component, and mass-marking old FxOS bugs as incomplete. If any of these bugs are still valid, please let me know.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.