GGitHub[path_provider] Revert iOS/macOS to plugin-based implementation (#10517 )

eda03017创建于 2025年11月26日历史提交

文件	最后提交记录	最后更新时间
darwin	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
example	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
lib	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
pigeons	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
test	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
.gitignore	[path_provider] Merge iOS and macOS implementations (#6988) * Rename directory; no changes * Exclude new plugin from build-all during the transition * Rename files and classes, update metadata * Make error messages non-macOS-specific * Move implementation to shared location * IGNORE IN REVIEW add symlinks * Add macOS symlink readme * Add iOS support with sharedDarwinSource * Add iOS example freshly created from template * Add iOS symlinks * Add missing library directory to example, for parity with iOS * Move unit test to shared location, and add iOS unit test target using it * Add the Swift search paths to podspec * Remove path_provider_ios * Update CODEOWNERS * Add copyrights to example files	3 年前
AUTHORS	[path_provider] Merge iOS and macOS implementations (#6988) * Rename directory; no changes * Exclude new plugin from build-all during the transition * Rename files and classes, update metadata * Make error messages non-macOS-specific * Move implementation to shared location * IGNORE IN REVIEW add symlinks * Add macOS symlink readme * Add iOS support with sharedDarwinSource * Add iOS example freshly created from template * Add iOS symlinks * Add missing library directory to example, for parity with iOS * Move unit test to shared location, and add iOS unit test target using it * Add the Swift search paths to podspec * Remove path_provider_ios * Update CODEOWNERS * Add copyrights to example files	3 年前
CHANGELOG.md	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
LICENSE	Remove "All right reserved" from all files (#10066) Per guidance from legal on current preferred practice, remove "All rights reserved" from all LICENSE files and header blocks, and update the repo tool check accordingly.	7 个月前
README.md	[various] Update flutter.dev links to more reliable destinations (#6963) Contributes to https://github.com/flutter/website/issues/10363 by updating to the latest links and updating some links to use new `/to/` links that can be updated as needed.	1 年前
pubspec.yaml	[path_provider] Revert iOS/macOS to plugin-based implementation (#10517) Reverts to the plugin-based implementation of `path_provider_foundation` while issues are being sorted out: - 2.5.0 (the FFI version) had to be retracted due to https://github.com/flutter/flutter/issues/178915 - Releasing a new FFI version that would fix that issue is blocked on https://github.com/dart-lang/native/issues/2824 - Our tree is also closed on https://github.com/dart-lang/native/issues/2824 as an OOB failure due to the `objective_c` 9.2.0 release. - Depending on `objective_c` 9.2.0 also appears to add new toolchain requirements for running Dart unit tests, which we will a) need to figure out in our CI, and b) decide if we are okay pushing onto users (https://github.com/flutter/flutter/issues/178715). This effectively reverts https://github.com/flutter/packages/pull/9762 (except for the changes allowing `ffigen` and `objective_c`, as Dart-team-owned dependencies). It was created by checking out the pre-9762 state of all the files in that directory, then applying `dart fix --apply` and `dart format` to pick up the changes for the new analyzer rules. Because of that PR landing, we can't just do a clean revert. Fixes https://github.com/flutter/flutter/issues/178915 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前

path_provider_foundation

The iOS and macOS implementation of path_provider.

Usage

This package is endorsed, which means you can simply use path_provider normally. This package will be automatically included in your app when you do, so you do not need to add it to your pubspec.yaml.

However, if you import this package to use any of its APIs directly, you should add it to your pubspec.yaml as usual.