Persistent Resource Manager & Smart Backup System (Safe Updates)

[aman-khan-786]

Issue Checklist

• I confirm that this feature request has not been previously suggested.
• I agree to follow the project's code of conduct.
• I have checked and verified that I am using the latest version of Code on the Go from GitHub or App Dev for All.

Additional terms

• I understand that feature requests are subject to evaluation and may not be implemented immediately.
• I agree to provide additional details if needed for a clearer understanding of the requested feature.

Feature description

I propose implementing a "Persistent Resource Manager" to handle heavy SDK/NDK files and project resources during app updates, uninstalls, or file corruption events. While the dev team is likely aware of Android's Scoped Storage wiping app data on uninstall, this feature request focuses on creating a seamless UX flow to bypass this limitation.

Key Mechanics:

1. Safe Export (Safe Haven): An option to compress and backup all core resources (SDKs, NDKs, Gradle caches) into a single ZIP file saved in a public directory (e.g., Documents/COTG_Backups) so it survives app deletion.
2. Auto-Detect & Restore: On a fresh install or post-update, the app automatically scans for this backup ZIP. If found, it prompts the user to auto-import and merge the resources.
3. Smart Merge: It safely replaces corrupted files while keeping intact resources, saving download time.
4. "Nuke Data" Option: A dedicated button in settings to completely wipe all COTG data AND the public backup file, giving the user total control if they want a 100% clean installation.

Use Case

Seamless Updates & Fixing Corrupted Environments:
Scenario: A user updates COTG to a newer version or reinstalls the app to fix a glitch. Currently, because of Android's storage rules, they lose all heavy SDK/NDK files and must re-download gigabytes of data. This is extremely painful for mobile developers on limited cellular data networks.

With this feature, a user can backup their environment, safely uninstall/update the app, and simply click "Restore" on the first launch. If a file gets corrupted during an update, the ZIP backup acts as a fail-safe. It transforms a frustrating OS limitation into a premium, user-friendly feature.

Benefits

• Massive Data Savings: Prevents redundant downloading of GBs of SDK/NDK files for users on limited mobile data.
• Instant Setup Post-Update: Developers can jump right back into coding immediately after updating the app.
• Prevents File Corruption: The safe ZIP archive prevents "ghost errors" and broken setups caused by corrupted files during in-app updates.
• Ultimate User Control: The "Nuke Data" option ensures that when a user actually wants to delete everything, no hidden junk files are left behind on their device.

[coderabbitai]

🔗 Related PRs

#1011 - ADFA-3007 | Add proactive low storage check and dialog [merged]
#1016 - ADFA-3085 | Fix ENOENT crash when saving chat sessions [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!