-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync should handle library/client errors #2316
Comments
#1149 related issue. I think we can go with something like: Title: Sync servers can't be reached cc: @tomlowenthal |
[Always blame the user 😛] |
Marking as |
@cezaraugusto can we get this in for 58.x too? Use toml text above/repeated here: Can you also create a test plan for QA. |
sure I'll be addressing this in a quick follow-up once sync v2 lands |
@cezaraugusto - in the test plan, should we see the error just by navigating to brave://sync or do we need to perform an action on the page (View Sync Code, Leave Sync Chain, Add Device, etc)? |
@cezaraugusto Verified the issue on 0.59.12. I am not seeing |
Verification passed on
Verified passed with
Verification passed on
Used test plan from description |
Sync should handle library/client errors. We have this mechanism in the back-end but interface should be aware of it.
The error happens when sync client (browser) can't connect with the sync server for N reasons, so the message needs to be generic.
Worth mentioning that the offline error is already handled so this is different.
cc @rebron @bradleyrichter to cook a good phrase for this.
Test Plan:
Couldn't contact Sync servers
error dialogThe text was updated successfully, but these errors were encountered: