MuntashirAkon/AppManager · error · IOException

Could not delete <mBackupPath>

Error message

Could not delete <mBackupPath>

What it means

At the end of a backup, BackupItem.finalize (backup mode) promotes the staged temp backup by first deleting any existing backup at mBackupPath. If delete() fails the item throws, because proceeding with the move would leave inconsistent backup state.

Source

Thrown at app/src/main/java/io/github/muntashirakon/AppManager/backup/BackupItems.java:473

            getFreezeFile().delete();
        }

        public boolean isFrozen() {
            try {
                return getFreezeFile().exists();
            } catch (IOException e) {
                return false;
            }
        }

        public void commit() throws IOException {
            if (mBackupMode) {
                if (mBackupSuccess) {
                    // Backup already done
                    return;
                }
                if (!delete()) {
                    throw new IOException("Could not delete " + mBackupPath);
                }
                if (!mTempBackupPath.moveTo(mBackupPath)) {
                    throw new IOException("Could not move " + mTempBackupPath + " to " + mBackupPath);
                }
                if (mPreviousBackups != null) {
                    for (BackupItem previousBackup : mPreviousBackups) {
                        if (!previousBackup.delete()) {
                            Log.w(TAG, "Could not delete %s", previousBackup.mBackupPath);
                        }
                    }
                }
                mBackupSuccess = true;
                // Set backup mode to false to make it read-only
                mBackupMode = false;
            }
        }

        public void cleanup() {

View on GitHub (pinned to 0152f468fc)

Solutions

1. Manually remove the stale backup at mBackupPath and retry the backup operation
2. Check storage permissions/mount status for the backup location
3. Retry the whole backup (it will re-create the temp backup)
4. Move backups to app-internal storage to avoid SAF quirks

Example fix

// before
new BackupItems.BackupItem(userId, name, pkg).close(); // may throw on delete failure
// after
try {
    new BackupItems.BackupItem(userId, name, pkg).close();
} catch (IOException e) {
    // clean up stale backup dir, then retry backup
}

// before finalizing: ensure backup path is deletable
File existing = new File(backupPath);
if (existing.exists() && !existing.delete()) { /* resolve lock/permission first */ }

try {
    backupItem.close();
} catch (IOException e) {
    if (e.getMessage().startsWith("Could not delete")) {
        // remove stale backup manually, then retry
    }
}

When it happens

Trigger: Closing/finalizing a BackupItem after backup when mBackupMode is true, backup not yet marked successful, and the existing backup directory/file at mBackupPath cannot be deleted.

Common situations: SAF or external-storage permission loss mid-backup, files locked by other processes, partial backups from a previous crashed run with odd permissions.

Understand the failure class

Background: "failed to write file", "Could not save figure", "Error saving remote file" — file write failed: causes and fixes across languages and libraries — this error's family across 38 libraries.

Related errors

• Couldn't delete old file <inputFile>
• Could not move <mTempBackupPath> to <mBackupPath>
• Could not create BackupItem.
• Android System (android) cannot be backed up.
• Backup is requested without any flags.

AI-assisted analysis of MuntashirAkon/AppManager@0152f468fc (2026-09-12). Data as JSON: /api/errors/5ed21c4df3473c19. Report an issue: GitHub.