Closed
Bug 1034612
Opened 10 years ago
Closed 10 years ago
Find My Device stage to prod switch results in constant 401 error
Categories
(Cloud Services Graveyard :: Find My Device, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: gerard-majax, Unassigned)
References
Details
Find My Device stage instance constantly returns a 401 error when used from my Flame, running latest master from today.
> 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] findmydevice alarm!
> 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] findmydevice attempting registration.
> 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] registering: false
> 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] refreshing client id if registered and logged in: {"registered":false,"loggedIn":true}
> 07-04 16:13:01.943 1036 1036 I GeckoDump: [findmydevice] findmydevice received push endpoint!
> 07-04 16:13:02.733 1036 1036 I GeckoDump: [findmydevice] findmydevice request failed with status: 401
This is quie blocking for bug 1000323, since it's very hard to be sure of the state of the system.
|
Reporter | |
Updated•10 years ago
|
blocking-b2g: --- → 2.0?
|
||
Comment 1•10 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #0)
> Find My Device stage instance constantly returns a 401 error when used from
> my Flame, running latest master from today.
>
> > 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] findmydevice alarm!
> > 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] findmydevice attempting registration.
> > 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] registering: false
> > 07-04 16:13:01.623 1036 1036 I GeckoDump: [findmydevice] refreshing client id if registered and logged in: {"registered":false,"loggedIn":true}
> > 07-04 16:13:01.943 1036 1036 I GeckoDump: [findmydevice] findmydevice received push endpoint!
> > 07-04 16:13:02.733 1036 1036 I GeckoDump: [findmydevice] findmydevice request failed with status: 401
>
> This is quie blocking for bug 1000323, since it's very hard to be sure of
> the state of the system.
ggp any idea if we are having server side issues recently ?
Flags: needinfo?(ggoncalves)
|
|
Reporter | |
Comment 2•10 years ago
|
||
And today it's working as far as I can tell.
|
|
||
Comment 3•10 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #2)
> And today it's working as far as I can tell.
clearing the nom in that case
Status: NEW → RESOLVED
blocking-b2g: 2.0? → ---
Closed: 10 years ago
Flags: needinfo?(ggoncalves)
Resolution: --- → WORKSFORME
|
|
Reporter | |
Comment 4•10 years ago
|
||
This has restarted.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
|
|
Reporter | |
Comment 5•10 years ago
|
||
Okay, my bad, it's probably because bug 1032938 relanded.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
|
|
Reporter | |
Comment 6•10 years ago
|
||
Sorry for the noise, but after disconnecting and reconnecting, I can confirm that with the landing of production server (bug 1032938) one has to factory reset its device if Find My Device was previously enabled ...
|
|
Reporter | |
Updated•10 years ago
|
|
Assignee | |
Updated•9 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•