Skip to content
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

Firestore uses the File timestamp APIs but has not provided a reason in the privacy manifest. #12803

Closed
edisonlin77 opened this issue Apr 17, 2024 · 2 comments
Assignees

Comments

@edisonlin77
Copy link

Description

I found that Firestore uses the stat function in the File timestamp APIs, please add reason for use in privacy manifest.

Reproducing the issue

No response

Firebase SDK Version

10.24.0

Xcode Version

15.2

Installation Method

Swift Package Manager

Firebase Product(s)

Firestore

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@ncooke3
Copy link
Member

ncooke3 commented Apr 18, 2024

Hi @edisonlin77, Firestore does not directly use that API, but does depend on dependencies that do. Those dependencies have privacy manifests to justify the usage of the API, but the privacy manifests are not being evaluated by the App Store Connect validator. Let's continue the conversation in #12557.

@ncooke3 ncooke3 closed this as completed Apr 18, 2024
@ncooke3 ncooke3 closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
@firebase firebase locked and limited conversation to collaborators May 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants