-
Notifications
You must be signed in to change notification settings - Fork 663
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
tracing_appender
triggers Apple NSPrivacyAccessedAPICategoryFileTimestamp
API usage warning
#2918
Comments
jamilbk
changed the title
Don't rely on file creation timestamps
Mar 28, 2024
tracing_appender
: Don't rely on file creation timestamps
jamilbk
changed the title
Mar 28, 2024
tracing_appender
: Don't rely on file creation timestampstracing_appender
: Don't rely on file creation timestamps for core functionality
jamilbk
changed the title
Mar 29, 2024
tracing_appender
: Don't rely on file creation timestamps for core functionalitytracing_appender
: Don't rely on reading file creation timestamps for core functionality
jamilbk
changed the title
Mar 29, 2024
tracing_appender
: Don't rely on reading file creation timestamps for core functionalitytracing_appender
triggers Apple NSPrivacyAccessedAPICategoryFileTimestamp
API usage warning in App Store
jamilbk
changed the title
Mar 29, 2024
tracing_appender
triggers Apple NSPrivacyAccessedAPICategoryFileTimestamp
API usage warning in App Storetracing_appender
triggers Apple NSPrivacyAccessedAPICategoryFileTimestamp
API usage warning
|
Yeah, we ended up just submitting a PrivacyManifest because even Here is what Apple approved if it's helpful for anyone else: https://github.com/firezone/firezone/blob/main/swift/apple/PrivacyInfo.xcprivacy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Crates
tracing_appender
Motivation
Apple's new Privacy regulations force developers to now declare a "Privacy Manifest" file
with details on why the API in question is needed.
tracing_appender
seems to use theNSPrivacyAccessedAPICategoryFileTimestamp
API in its operation here.This creates a hurdle for building applications for Apple platforms that use tracing_appender as it reads file timestamps by default.
See the error message we received from the App Review team.
Proposal
I suppose there's not a great solution for this. In our case, the filenames themselves have the creation timestamp in them, so tracing_appender may be able to use that.
Otherwise, perhaps exposing an option to prevent this from being linked in at compile-time would be sufficient, like perhaps behind a feature. We tested without rollover (so this codepath should not be hit at runtime) and it still triggered Apple's warning.
Alternatives
Unfortunately we're considering just removing tracing_appender altogether and rolling our own non-blocking log writer that doesn't read file timestamp metadata. :-(
The text was updated successfully, but these errors were encountered: