ImagePicker is redirected to the ASD for Android 10+

[Anke]

@ewpatton

I definitely agree that the storage requirements are confusing. I'll have to run some tests on Android 9, 10, and 11 to better understand exactly what's going on here

I know there is a lot to do right now.
But if there is any new insight on this, please let us know.

[Mr_Czechowski]

@ewpatton

... components like Canvas will not since they don't save to the shared directories.

Will it eventually be possible for Canvas (and those other components) to save into a Shared folder?

[Anke]

[Mr_Czechowski]

Thank you @Anke that is very clear!

Follow-up: Returning to the subject of this thread... will ImagePicker be able to access the Shared directory? Would it be appropriate for ImagePicker to use the DefaultFileScope (Shared vs ASD vs Legacy)?

I do not yet have a recent Android Device to test this on.

[Anke]

@Mr_Czechowski

will ImagePicker be able to access the Shared directory?

Yes.

@Mr_Czechowski

Would it be appropriate for ImagePicker to use the DefaultFileScope (Shared vs ASD vs Legacy)?

It doesn't matter here.

[Mr_Czechowski]

@vknow360

But the actual behaviour should be to allow user to pick files from whole storage and not only from ASD, because ASD is only accessible to that particular app.

Something like this would be nice: swift - App's own image folder in UIImagePickerController - Stack Overflow

[Anke]

@Mr_Czechowski

Something like this would be nice: swift - App's own image folder in UIImagePickerController - Stack Overflow

This refers to iOS / Swift.

[Mr_Czechowski]

Yes, but I thought the user experience presented at the link might be generalizable in the way it addresses:

How should the ImagePicker present the user with resources in both private storage (ASD) & shared storage?