-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for capturing data in extensions #141
Comments
This issue is stale because it has been open for 30 days with no activity. Remove the Stale label or comment or this will be closed in 10 days. |
Comment to prevent from closing. |
This issue is stale because it has been open for 30 days with no activity. Remove the Stale label or comment or this will be closed in 10 days. |
Bump |
This issue is stale because it has been open for 30 days with no activity. Remove the Stale label or comment or this will be closed in 10 days. |
Hey team. I really like this library. A+! One thing that would make it that much better would be explicit support for app extensions. In my analysis of the library it looks like most of it if not all of it would work out of the box in an app extension, but not all extensions have UI that can be presented so I'd need to change the file location to live within an app group container.
For example, I would want to be able to add custom logs within a widget extension, live activity, share extension, etc. Then, later on, because the file lives in the app group, the main app could export it on behalf of the user in what ever workflow.
I think that the access to then files would be safe across extension / app concurrently because of the use of the NSFileCoordinator and the only thing that would have to change would be to allow injection (or specification) of the log file destination.
The text was updated successfully, but these errors were encountered: