-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Firebase files appears on Files.app #2984
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
Comments
Related: #843 |
@ryanwilson so this reported year ago and still not fixed? Isn’t there any workaround? |
@fawzirifai it was reported for a different product (Firestore vs RTDB) but the underlying issue is the same, yes. The migration aspect is the most difficult and requires care since it affects user data and un-synced changes could be lost if something goes wrong. Unfortunately there's not a great workaround for this that I'm aware of. |
Its 2021 and still not fixed |
Having the same issue #10036 three years after the initial issue was posted. Please consider fixing this. |
This is still an existing issue towards the end of 2023. When enabling access via files app the LBD data is accessible by the user. |
+1 for a fix. The fact that data is visible to the user and can possibly be exported/processed should not be the default for projects. I am really hoping for a fix or a workaround as my data should be displayed in the app but under no circumstances be exportable. |
Uh oh!
There was an error while loading. Please reload this page.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
When I opting the app to be appeared in the Files app, there is a Firebase folder that contains “server_data” and “writes” folders and inside each of them there are multiple files, I think the Firebase folder should be hidden, right?
Steps to reproduce:
Opt in with Files app: Add these keys to your Info.plist and set their values to YES: "Application supports iTunes file sharing" and "Supports opening documents in place", then run the app.
The text was updated successfully, but these errors were encountered: