FYI The following information is from a previous post that may help.
The trashcan is not displayed if the browser version is less than v1.18.19 which is very old. Prior to this version browser does not support self-delete, so there is no trashcan icon next to such devices.
In your case I doubt you had such old version, but I don’t understand why happens. You can check it at brave://sync-internals/ => Sync Node Browser tab => Device info => choose your device => check MTIME field, it corresponds to the last time when the device was active, and chrome_version field to check the version. This may help to understand why there is no trashcan button.I got a laptop stolen and now I cannot remove that device from the Sync chain
opened 06:25AM - 17 May 22 UTC
closed 07:49PM - 20 Dec 22 UTC
security
feature/sync
QA Pass-Win64
QA Pass-macOS
QA Pass-Linux
QA/Yes
release-notes/include
QA/Test-Plan-Specified
OS/Android
QA Pass - Android ARM
OS/Desktop
QA/Test-All-Platforms
A user who wants to stop using Sync should have the ability to delete their encr… ypted data from our server. Next to the “Leave Sync chain” button at the bottom of the page, we should have a “Delete Sync account” button. It would trigger the following confirmation dialog:
```
Deleting your account will remove your encrypted data from Brave servers and
disable Sync on all of your connected devices.
It will not however delete the data that is stored locally on those devices.
This deletion is permanent and there is no way to recover the data. Should you decide to
start using Sync again, you will need to create a new account and re-add each device one by one.
[ Permanently delete account ] [ Cancel ]
```
Spec: https://docs.google.com/document/d/1X7glDHmeIjgipcPWn__S9rSxrI39P9rNw0RmuEuC3BI/edit#heading=h.f9zbg4b885l
brave:master ← brave:sync_perman_del_acc
opened 03:32PM - 01 Jun 22 UTC
Resolves https://github.com/brave/brave-browser/issues/22884
This PR introduc… es ability to permanently delete the sync chain for desktop and Android.
Related server changes: https://github.com/brave/go-sync/compare/102-add-account-delete
## Submitter Checklist:
- [x] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have [requested](https://github.com/brave/security/issues/1093) one - requested
- [x] There is a [ticket](https://github.com/brave/brave-browser/issues) for my issue
- [x] Used Github [auto-closing keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in the PR description above
- [x] Wrote a good [PR/commit description](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
- [x] Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
- [x] Added appropriate labels (`QA/Yes` or `QA/No`; `release-notes/include` or `release-notes/exclude`; `OS/...`) to the associated issue
- [x] Checked the PR locally: `npm run test -- brave_browser_tests`, `npm run test -- brave_unit_tests`, `npm run lint`, `npm run gn_check`, `npm run tslint`
- [x] Ran `git rebase master` (if needed)
## Reviewer Checklist:
- [ ] A security review [is not needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or a link to one is included in the PR description
- [ ] New files have MPL-2.0 license header
- [ ] Adequate test coverage exists to prevent regressions
- [ ] Major classes, functions and non-trivial code blocks are well-commented
- [ ] Changes in component dependencies are properly reflected in `gn`
- [ ] Code follows the [style guide](https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md)
- [ ] Test plan is specified in PR before merging
## After-merge Checklist:
- [ ] The associated issue milestone is set to the smallest version that the
changes has landed on
- [ ] All relevant documentation has been updated, for instance:
- [ ] https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
- [ ] https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
- [ ] https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
- [ ] https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
- [ ] https://github.com/brave/brave-browser/wiki/Custom-Headers
- [ ] https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
- [ ] https://github.com/brave/brave-browser/wiki/QA-Guide
- [ ] https://github.com/brave/brave-browser/wiki/P3A
## Test Plan:
Pls see https://github.com/brave/brave-core/pull/13562#issuecomment-1267349520