Description

For iOS, NSLibraryDirectory are more used for application data like sqlite.db or images which would like to be capacity to persistent, backed up and not visible in iTunes File Sharing when UIFileSharingEnabled is TRUE in app's plist file.

From StackOverFlow discuss: Path Directory Usable in iOS

• NSDocumentDirectory is Documents/ (persistent, backed up, may be visible in iTunes)
• NSLibraryDirectory is Library/ (persistent, backed up, not visibe to the user)
• NSCachesDirectory is Library/Caches/ (not backed up, may be cleared by system)

From iOS framework:

• NSLibraryDirectory, // various documentation, support, and configuration files, resources (Library)
• NSApplicationSupportDirectory = 14, // location of application support files (plug-ins, etc) (Library/Application Support)

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
• I updated CHANGELOG.md to add a description of the change.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.