melonDS-android v0.7.0.rc3 Hotfix is now available.

This hotfix fixes a ROM launch issue caused by Android/Google Backup restoring old app data without restoring the required ROM folder permissions.

On some devices, this could cause games to crash, return to the ROM list, or fail right after the Loading screen.

This version disables Android Auto Backup for the app and adds safer validation around restored ROM folders, cached ROM data, and auto-load savestates.

Important:

If games still fail to start after updating to this hotfix, please uninstall and reinstall the app once.
This version disables Android backup restore, so reinstalling should now correctly clear the stale restored data that caused the issue.
After reinstalling, re-authorize your ROM folder from Settings if needed.

Diagnostics:

• New System setting: Write app log to ROM folder

  • When enabled, the app writes melonDualLog.log into the ROM folder.
  • This log includes app, native, and core logs.
  • It is intended to help debug rare launch, renderer, or device-specific issues.

• Safer RetroAchievements diagnostic logs

  • RetroAchievements login now includes safer diagnostic logging.
  • Logs do not write usernames, passwords, or session tokens.

Fixed:

• Improved ROM folder permission validation

  • If rom_search_dirs exists but the app no longer has persistent read permission, the restored cache is no longer trusted.
  • The app now shows a dialog asking the user to re-authorize the ROM folder from Settings.
  • This prevents broken restored state from blocking normal ROM launching.

• Improved auto-load savestate safety

  • auto_load_state_on_launch now validates the savestate header before loading.
  • If the auto-load savestate is invalid or cannot be loaded, the ROM now continues booting normally.
  • A warning toast is shown instead of blocking the game launch.

Please keep testing RC3 so we can make the final 0.7.0 release more stable for everyone.

Thank you for supporting the project and helping improve melonDS Android.