- Create a funnel class that logs the appropriate status code + url that was attempted (we do this for all metrics). This may already partially be done in https://github.com/wikimedia/wikipedia-ios/pull/5716.
- (Legacy) Inspect status codes at the various appropriate locations in Session.swift and log via funnel class if code is >= 400.
- (Modern) Inspect status codes in WMFBasicService and log via funnel class if code is >= 400. In this case we will need to call a generic closure via WMFDataEnvironment to allow callback to the funnel class.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
Match Android behavior - log errors so they can be monitored. Helps with understanding issues like rate-limited
Comment Actions
Doing this task would help us better understand how to fix these two bugs:
T426463: Error on full-screen image open
T341898: Bug: Error 'WMF.RequestError error 0'
Comment Actions
Not really an easy way to QA this, but we can watch the dashboard for events coming from external beta.
Comment Actions
Signed off from my POV if Anthony is happy with watching the dashboard for events coming from external beta