How to uninstall TickTick (滴答清单) on Mac
TickTick keeps your tasks, lists and habits in your account and syncs them, so removing the Mac app deletes none of them, and deleting the account is a separate step on the web. The build tested here is TickTick from ticktick.com, bundle ID com.TickTick.task.mac. The app also carries the Chinese name 滴答清单, and on a Mac set to Simplified Chinese it can appear under that name; Mole showed it that way in one test. The 滴答清单 download from dida365.com was not tested, so this guide does not claim its paths match. The guide covers the ticktick.com download and the Homebrew cask ticktick.
Before you remove it
- If you want a copy of your data outside TickTick, the web app can generate a backup file from its settings. On 滴答清单 the path is 设置 › 数据备份 › 生成备份.
- To delete the account instead of just the app, sign in on the web, open Settings › Profile and choose Delete account, as TickTick's guide describes. That removes all your data from TickTick, and uninstalling the app never does it for you.
Quit and remove the app
- Quit TickTick with Command + Q. Status showed it as one row with two processes and about 52 MB.
- Move TickTick from Applications to the Trash. Its widgets and its Safari extension ship inside the app and go with it.
- Open System Settings › General › Login Items & Extensions. TickTick carries a launch-at-login helper, and in the September 20 test its entry was still listed after the uninstall, pointing at the app in the Trash. Turn it off if you see it.
Where the app keeps its data
Press Shift + Command + G in Finder and open each location, skipping any that is missing. TickTick does not document these paths; they come from Homebrew's zap list and the recorded tests.
| Location | What it holds | What to do |
|---|---|---|
~/Library/Group Containers/75TY9UT8AY.com.TickTick.task.mac and ~/Library/Application Scripts/75TY9UT8AY.com.TickTick.task.mac |
The group folder the app shares with its widgets, 2.8 MB after one launch without signing in, and its script folder | Remove them once your tasks are synced |
~/Library/Containers/com.TickTick.task.mac.MainWidget and ~/Library/Containers/com.TickTick.task.mac.TickTick-Safari-Extension |
Containers of the widget and the Safari extension, with matching folders under ~/Library/Application Scripts |
Remove them with the app |
~/Library/Preferences/com.TickTick.task.mac.plist |
Preferences | Remove it with the app |
~/Library/Caches/com.TickTick.task.mac, ~/Library/HTTPStorages/com.TickTick.task.mac |
Cache and network storage, plus a cookies file beside them | Safe to remove |
~/Library/Application Support/bugsnag-shared-com.TickTick.task.mac, ~/Library/Caches/bugsnag-shared-com.TickTick.task.mac, ~/Library/Application Support/com.bugsnag.Bugsnag/com.TickTick.task.mac |
Crash-reporter files from the Bugsnag library | Safe to remove; leave the com.bugsnag.Bugsnag parent, other apps can use it |
Files under ~/Library/Biome whose path contains sourceIdentifier=com.TickTick.task.mac belong to macOS: they record the actions the app offers to Siri and the Shortcuts app. Leave them to the system.
Check the result
Run these read-only commands after the app is in the Trash:
pgrep -il ticktick
ls -d "$HOME/Library/Group Containers/75TY9UT8AY.com.TickTick.task.mac" ~/Library/Containers/com.TickTick.task.mac.MainWidget
- No output from
pgrepmeans TickTick is not running. A listed process means it is still open. ls -dprints each folder that still exists. The group folder surviving is expected if you left it unticked in Mole. "No such file or directory" means that folder is gone.
If you installed it with Homebrew
When you remove a Homebrew install, Mole runs Homebrew's uninstall and adds --zap only when every path in the cask's zap list sits inside ~/Library, none of them is a row you left unticked, and no other installed app claims it. Otherwise it leaves --zap out and still removes the rows you ticked.
The ticktick cask's zap list covers the group folder ~/Library/Group Containers/75TY9UT8AY.com.TickTick.task.mac, every com.TickTick.task.mac.* container and script folder, ~/Library/Application Support/com.TickTick.task.mac, the Bugsnag folders, the caches including ~/Library/Caches/TickTick, the HTTPStorages entries, the preferences file and the saved window state. The group folder is a row Mole leaves unticked by default, so Mole leaves --zap out unless you tick it. brew uninstall --cask --zap ticktick moves all of them to the Trash whatever you ticked in Mole. To remove only the app:
brew uninstall --cask ticktick
Delete a TickTick account · 滴答清单: back up your data · Homebrew's ticktick cask
What Mole lists
For TickTick downloaded from ticktick.com:
- The preferences file, the cookies file, the cache, HTTPStorages, the Bugsnag folders and the temporary folders macOS keeps for the app are selected by default.
- The containers and Application Scripts folders of the widget and the Safari extension,
com.TickTick.task.mac.MainWidgetandcom.TickTick.task.mac.TickTick-Safari-Extension, are selected by default, because both ship inside TickTick.app. - The group folder
75TY9UT8AY.com.TickTick.task.macand its Application Scripts peer are listed but not selected. When you tick them, Mole first checks that no other installed app uses the group; if it cannot confirm that, it keeps the folder and the row says so. - Files under
~/Library/Biomeare not listed.
What this test covered
On September 26, 2026, TickTick 8.2.30 was copied from the official download into Applications, without Homebrew, launched once without signing in, and uninstalled with a development build of Mole, with every listed item ticked for the test. Status showed one row, TickTick, with two processes and about 52 MB. The app and all 14 listed rows went to the Trash, the 2.8 MB group folder included. What remained were six database files under ~/Library/Biome that macOS manages. No startup item appeared before or after. An earlier test on September 20, 2026 used TickTick 8.2.10 from the official package with Mole 1.15 Preview build 280, which showed the app as 滴答清单: with everything ticked, the 2.6 MB group folder was kept, the widget's 4 KB container could not be moved because macOS refused permission, and the login item stayed listed, pointing at the Trash. Neither test signed in, so account sync was not checked, and the Homebrew cask was not tested.
