Closed Bug 1028868 Opened 10 years ago Closed 10 years ago

Handle Push Server "Register" failures

Categories

(Hello (Loop) :: Client, defect, P4)

Product:
Hello (Loop)
Component:
Client
Type:
defect

Tracking

(firefox34 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla34
Tracking Flags:
Tracking Status
firefox34 --- fixed

People

(Reporter: standard8, Unassigned)

References

Details

(Whiteboard: [p=2, gecko?][fixed by bug 1002414])

User Story

https://wiki.mozilla.org/WebAPI/SimplePush/Protocol

We need to handle the possibility of failure of the register method, and update the xpcshell-tests to cover it.
No description provided.
Unsure how likely we are to hit this on production. Hence not sure as to the priority/target.
User Story: (updated)
Whiteboard: [p=2]
OS: Mac OS X → All
Hardware: x86 → All
Priority: -- → P2
Target Milestone: --- → mozilla33
Target Milestone: mozilla33 → mozilla34
when you get back - is this something we can push off or wait to see? or is this Gecko enough we can ask webRTC versus contact (maire's question)?
Flags: needinfo?(standard8)
Priority: P2 → P4
Whiteboard: [p=2] → [p=2, gecko?]
The changes implemented in bug 1002414 have fixed this nicely.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(standard8)
Resolution: --- → FIXED
Whiteboard: [p=2, gecko?] → [p=2, gecko?][fixed by bug 1002414]
Does this need manual testing or is it sufficient covered in-testsuite?
Flags: qe-verify?
Mark, can you please answer comment 4?
Flags: needinfo?(standard8)
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #4) > Does this need manual testing or is it sufficient covered in-testsuite? The answers in bug 1002414 are valid for this bug as well.
Flags: needinfo?(standard8)
Flags: qe-verify? → qe-verify-
status-firefox34: --- → fixed
QA Contact: anthony.s.hughes
You need to log in before you can comment on or make changes to this bug.