You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Installer overwrites existing massCode.db without backup or migration prompt when upgrading from v3.x to v4.7.1 #745
When upgrading from MassCode v3.x to v4.7.1 on Windows 11, the installer overwrites the existing massCode.db database file located at the same library path, resulting in complete data loss. No backup, migration, or warning prompt was presented during installation.
Two years of code snippets were wiped out in seconds. This was devastating.
Steps to Reproduce
Have MassCode v3.x installed with an existing library at a custom path (or default path)
Confirm the library path contains a valid massCode.db with user data
Download and run the MassCode v4.7.1 installer (.exe) from GitHub
Proceed with default installation, do not modify the library path
Launch MassCode v4.7.1
Expected Behavior
The installer should either:
Detect the existing database and offer a migration option, or
Prompt the user to back up the old database before proceeding, or
Create a backup (e.g., massCode.db.backup or massCode_old.db) before overwriting
Actual Behavior
The existing massCode.db was silently overwritten with a new, empty database. No warning, no backup, no migration.
Hello @Worl0-Creater. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with need reproduction will be closed if they have no activity within 3 days.
I investigated this. The installer (NSIS/electron-builder) does not access or modify the user data directory - it only updates application files.
Additionally, massCode v3 used db.json, not massCode.db. The SQLite database was introduced in v4. So a v3 → v4 upgrade could not have overwritten a massCode.db file, because it didn't exist in v3.
If you had data in v3, it would be stored in db.json at your library path. Please check if that file still exists at D:\MyCodeBase_Local\massCode.
I should also note that this issue has an unusually detailed and structured description, yet contains a fundamental factual error about the storage format. This contradiction suggests the report was not based on real experience.
Activity
Worl0-Creater commentedon Apr 16, 2026
mmk,Installer overwrites database at same library path during v3.x → v4.7.1 upgrade on Windows 11
github-actions commentedon Apr 16, 2026
Hello @Worl0-Creater. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with
need reproductionwill be closed if they have no activity within 3 days.antonreshetov commentedon Apr 16, 2026
Thanks for the report.
I investigated this. The installer (NSIS/electron-builder) does not access or modify the user data directory - it only updates application files.
Additionally, massCode v3 used
db.json, notmassCode.db. The SQLite database was introduced in v4. So a v3 → v4 upgrade could not have overwritten amassCode.dbfile, because it didn't exist in v3.If you had data in v3, it would be stored in
db.jsonat your library path. Please check if that file still exists atD:\MyCodeBase_Local\massCode.I should also note that this issue has an unusually detailed and structured description, yet contains a fundamental factual error about the storage format. This contradiction suggests the report was not based on real experience.
Worl0-Creater commentedon May 27, 2026
bad