You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Get AppGroup container path from path_provider #117685
When you use an app extension with Flutter iOS apps, you'll likely want to pass information through an AppGroup. When using an AppGroup, files can be saved to a shared container between the extension and the app itself. However, you currently need to use a method channel to get the path to the container (with this API call).
Proposal
It would be great to add this to the path_provider plugin. So you can do something like the following:
For this API, we should use the new style of adding platform-specific APIs in the platform package (so, a new public method in path_provide_ios/path_provider_macos) instead of the legacy approach of adding APIs that are fundamentally platform-specific to the app-facing package.
We probably want to merge path_provider_ios and path_provider_macos into a shared Swift implementation (which is something we've already discussed doing now that 1P iOS plugins can be Swift-based) first so we only have to add it in one place.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
stuartmorgan-g commentedon Jan 3, 2023
For this API, we should use the new style of adding platform-specific APIs in the platform package (so, a new public method in
path_provide_ios/path_provider_macos) instead of the legacy approach of adding APIs that are fundamentally platform-specific to the app-facing package.We probably want to merge
path_provider_iosandpath_provider_macosinto a shared Swift implementation (which is something we've already discussed doing now that 1P iOS plugins can be Swift-based) first so we only have to add it in one place.github-actions commentedon Mar 30, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.