Great question! Capturing uninstall events directly in Electron isn't natively supported because app uninstall workflows are handled entirely by the operating system, not the app itself. But depending on how you package and distribute your app, there are reliable platform-specific workarounds to trigger your database update. Let's break them down:

Windows #

On Windows, uninstalls are managed via the system's Add/Remove Programs (or Settings > Apps), so you can hook into the uninstall process using your installer tool:

• If using electron-builder with NSIS: Configure a custom uninstall script in your package.json. This script will run automatically when the user initiates an uninstall via the system:

  {
    "build": {
      "nsis": {
        "uninstallScript": "scripts/uninstall.js"
      }
    }
  }
  

  In uninstall.js, write your database update logic (e.g., a POST request to your backend):

  const axios = require('axios');
  
  async function markUninstalled() {
    try {
      await axios.post('https://your-api.com/user/uninstall', {
        userId: 'user-unique-id' // Fetch this from local storage or a config file
      });
    } catch (err) {
      // Handle offline scenarios if needed (e.g., log to a local file for later retry)
      console.error('Failed to update database:', err);
    }
  }
  
  markUninstalled();
  

• For WiX or other installers: Add a custom action in your installer configuration that executes your cleanup script during the uninstall sequence.

macOS #

macOS doesn't have a formal uninstall process—users typically drag the app bundle to the Trash. This makes direct event capture tricky, but here are two solid approaches:

• Provide an official uninstaller: Bundle a small helper app or shell script with your main app, and prompt users to use it instead of dragging to Trash. The uninstaller can run your database update logic before deleting the app files.
• Background heartbeat + server-side cleanup: Have your app send a "heartbeat" request to your server every time it launches (or at regular intervals). Your server can then mark users as uninstalled if they haven't sent a heartbeat in a set period (e.g., 30 days). This is a reliable fallback even if users delete the app manually.

Linux #

Linux uninstalls are handled by package managers (APT, RPM, etc.), so you can leverage post-uninstall hooks in your package configuration:

• For DEB packages: Create a postrm script in your package's DEBIAN directory. This script runs after the app is removed:

  #!/bin/sh
  # Execute your database update script
  node /opt/YourApp/scripts/uninstall.js
  exit 0
  

• For RPM packages: Add a %postun section in your spec file that triggers your cleanup logic.

Universal Fallback: Server-Side Inactivity Tracking #

No matter the platform, some users will bypass official uninstall processes (e.g., deleting files directly). To cover these cases:

• Track app launches or periodic check-ins from the client to your server.
• Set up a server-side cron job or scheduled task that marks users as uninstalled if they haven't been active for a defined threshold (adjust based on your user base—14-30 days is common).

Key Notes #

• Offline Handling: If a user uninstalls without internet access, your script won't be able to update the database immediately. For critical cases, you could log the uninstall event to a local file and have a separate background process (if allowed by the OS) retry the request later. But keep in mind, once the app is uninstalled, this process will be gone too.
• User Privacy: Always inform users in your privacy policy that you track uninstalls or app activity for this purpose.

内容的提问来源于stack exchange，提问作者Vishal Shori