Surface sync errors and warnings in a more detailed and contextual way

NEW
Unassigned

Status

()

P3
normal
Rank:
2
2 years ago
11 months ago

People

(Reporter: sleroux, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MobileCore])

(Reporter)

Description

2 years ago
After the minor refactoring of how we resolve sync statuses into an error we can display to the user, it became apparent that we need a more intelligence in the way we resolve errors in the sync engines for the user. 

1. Adding context as to how the sync operation was instantiated. We probably want to show errors differently when sync operations happen automatically in the background vs when they were user initiated. 

2. Be more explicit about certain types of errors. We support a limited amount of messaging around the errors - including some that need some rewording such as 'Sync is offline'. Does this mean the servers are offline or am I offline?

3. Adding a notion of staleness/time to errors states. For example, if we haven't synced in a day or two, surface to the user that we haven't been able to sync in the past X days.

Updated

2 years ago
Priority: -- → P2
Whiteboard: [MobileAS Backlog]

Updated

2 years ago
Priority: P2 → --

Updated

2 years ago
Whiteboard: [MobileAS Backlog] → [MobileAS]

Updated

2 years ago
Priority: -- → P3

Updated

2 years ago
Whiteboard: [MobileAS] → [MobileAS] [needs trello card]

Updated

2 years ago
Rank: 2
Whiteboard: [MobileAS] [needs trello card] → [MobileCore] [needs trello card]
Whiteboard: [MobileCore] [needs trello card] → [MobileCore] [papercuts]
Whiteboard: [MobileCore] [papercuts] → [MobileCore] [papercut]
Whiteboard: [MobileCore] [papercut] → [MobileCore] [FxA]

Updated

11 months ago
Whiteboard: [MobileCore] [FxA] → [MobileCore]
You need to log in before you can comment on or make changes to this bug.