Replaced getApplicationDocumentsDirectory() with getApplicationSupportDirectory in io.dart

[neelkanth-kaushik]

This PR does following:

1. Replaces getApplicationDocumentsDirectory() with getApplicationSupportDirectory so that SDK files are not publically visible.

2. Moves the JSON files from Old directory to New directory.

3. When storageJson is turned on, the queued events are no longer deleted from the analytics-flutter-queue_flushing_plugin.json file if they cannot be sent due to any reason (ex. Network Error). They are attempted again according to the Flush policy.

[Copilot]

Pull Request Overview

This PR updates the directory selection strategy in the store implementation by replacing the use of getApplicationDocumentsDirectory() with getApplicationSupportDirectory() for better alignment with platform conventions.

• Switched from documents directory to application support directory for data storage

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

This change modifies where application data is stored, which could be a breaking change for existing users. Consider implementing a migration strategy to move existing data from the documents directory to the application support directory, or provide a configuration option to maintain backward compatibility.

Suggested change

	return await getApplicationSupportDirectory();
	final newDir = await getApplicationSupportDirectory();
	final oldDir = await getApplicationDocumentsDirectory();
	// Migrate old files if they exist
	final oldFiles = oldDir
	.listSync()
	.whereType<File>()
	.where((file) => file.path.contains('analytics-flutter-') && file.path.endsWith('.json'));
	for (final oldFile in oldFiles) {
	final fileName = oldFile.uri.pathSegments.last;
	final newFile = File('${newDir.path}/$fileName');
	if (!await newFile.exists()) {
	await oldFile.copy(newFile.path);
	await oldFile.delete();
	}
	}
	return newDir;

[Copilot]

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The catch block silently ignores all exceptions during file operations. Consider logging the error for debugging purposes while still allowing the app to continue.

Suggested change

	} catch (e) {
	// The app should continue to work even if migration fails
	}
	}
	}
	} catch (e) {
	// Migration failure shouldn't break the app
	} catch (e, stackTrace) {
	// The app should continue to work even if migration fails
	print('File migration error: \$e');
	print(stackTrace);
	}
	}
	}
	} catch (e, stackTrace) {
	// Migration failure shouldn't break the app
	print('Migration failure: \$e');
	print(stackTrace);

[Copilot]

The catch block silently ignores all exceptions during migration. Consider logging the error for debugging purposes while still allowing the app to continue.

Suggested change

	// The app should continue to work even if migration fails
	}
	}
	}
	} catch (e) {
	// Migration failure shouldn't break the app
	// The app should continue to work even if migration fails
	print('Error migrating file ${oldFile.path} to $newFilePath: $e');
	}
	}
	}
	} catch (e) {
	// Migration failure shouldn't break the app
	print('Error during migration from Documents to Support directory: $e');

[Copilot]

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}