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

Use sub-directories in the file provider #26989

Closed

Conversation

Redth
Copy link
Member

@Redth Redth commented Jan 7, 2025

On Android, it's a better practice to scope the paths used in a FileContentProvider as much as possible. Currently we just use the root . path for each area, even though we always seem to save temp files to 2203693cc04e0be7f4f024d5f9499e13 as a subfolder.

This updates our provider file paths to scope to that folder.

Related to #27685

On Android, it's a better practice to scope the paths used in a FileContentProvider as much as possible.  Currently we just use the root `.` path for each area, even though we always seem to save temp files to `2203693cc04e0be7f4f024d5f9499e13` as a subfolder.

This updates our provider file paths to scope to that folder.
@jfversluis jfversluis added the area-essentials Essentials: Device, Display, Connectivity, Secure Storage, Sensors, App Info label Jan 9, 2025
@mattleibow
Copy link
Member

Closing this as we need to first discuss what we want it to do. Not super high priority as there is a supported way to do this using the APIs provided. A better default can be discussed in the issue.

Also, this PR is probably breaking so we need to move this to .NET 10.

@mattleibow mattleibow closed this Feb 10, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Mar 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-essentials Essentials: Device, Display, Connectivity, Secure Storage, Sensors, App Info
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants