storage-diag

Files disappear after restart when stored in temporary locations like Caches or Tmp rather than persistent directories. Diagnose storage location, file protection level, and backup status to determine if files are in the wrong directory or excluded from backups unexpectedly.

Large backups typically result from files stored in Documents or Library that should be excluded. Check which files are being backed up, verify backup exclusion settings, and confirm storage location choices match your app's data retention strategy.

File inaccessibility when locked indicates a file protection mismatch. Verify the protection level assigned to each file—some require the device to be unlocked to read. Adjust protection settings and storage location based on when your app needs access.

File not found errors stem from incorrect storage location, missing backup restoration, or files deleted during cleanup. Follow a structured diagnosis: verify the storage directory is correct, check file existence, confirm backup status, and validate file protection settings.

Yes. Storage location determines persistence and backup inclusion; protection level controls when files are readable; and backup exclusions prevent unnecessary data bloat. These three factors resolve 90% of local storage problems without requiring OS-level fixes.

Store persistent data in Documents or Library, not Caches or Tmp. Exclude large or sensitive files from backups explicitly. Set appropriate file protection levels for your app's access patterns and data sensitivity requirements.