Adding logging to help the Support team troubleshoot auth issues our users are having.
Todos:
[x] Add response.status to our request errors
[x] Add logging to display the userId, token, guid, and where the guid came from
[x] Add logging to login page for userId and token as quick first step check
Implementation Decisions
It's difficult to reproduce the auth issues our users are running into, so I've added logging that our Support team can ask for.
The first bit of logging is for the getpocket.com/extension_login_success page. If this page hangs, you can open the console and verify whether there is a stored cookie for token or userId. These cookies should be created on the previous page.
The second bit of logging is displays the userId, token, guid and where the guid originates. The guid can originate from extension (stored in chrome.storage), site (stored in a cookie as sess_guid), or server (fetched from v3/guid). There should be 4 values in this object.
The last bit is adding the response.status to our request error handler. This way it's surfaced in the extension service worker console instead of needing to dig for it within the network panel.
Goal
Adding logging to help the Support team troubleshoot auth issues our users are having.
Todos:
response.statusto our request errorsuserId,token,guid, and where theguidcame fromloginpage foruserIdandtokenas quick first step checkImplementation Decisions
It's difficult to reproduce the auth issues our users are running into, so I've added logging that our Support team can ask for.
The first bit of logging is for the
getpocket.com/extension_login_successpage. If this page hangs, you can open the console and verify whether there is a stored cookie fortokenoruserId. These cookies should be created on the previous page.The second bit of logging is displays the
userId,token,guidand where theguidoriginates. Theguidcan originate fromextension(stored inchrome.storage),site(stored in a cookie assess_guid), orserver(fetched fromv3/guid). There should be 4 values in this object.The last bit is adding the
response.statusto our request error handler. This way it's surfaced in the extension service worker console instead of needing to dig for it within the network panel.