Android support for content:// uri in the File class.

[andyduke]

Flutter does not support content:// uri in Android. I cannot use such a uri in the File class to read the attached file in Gmail (for example, when opening an attached file from an email through a flutter application via deep linking).

You can write a plugin that will read files at such a URI, but this will not be a cross-platform code, since you will have to remember that in Android, content:// uri files must be read through the plugin, and in iOS via File class.

It would be nice to support this type of uri in the File class on Android.

[zoechi]

You can write a plugin that will read files at such a URI, but this will not be a cross-platform code,

That's common that the platform implementation between Android and iOS are different.
Why do you think that would be a problem in this case?

[andyduke]

You can write a plugin that will read files at such a URI, but this will not be a cross-platform code,

That's common that the platform implementation between Android and iOS are different.
Why do you think that would be a problem in this case?

Because you have to check the platform in the dart-code, and read the file differently on different platforms. What is the advantage of Flutter then? After all, this difference can be hidden inside the file management classes.

[zoechi]

@andyduke you can provide it the same way from native to Dart from iOS and Android so that you don't know the difference on the Dart side.
I still don't see the problem.

[andyduke]

When a link to a file comes into my dart-code (via a deep link, from the document picker, etc), it is necessary to check if it is a content uri and read it either through the File class or through a plugin. Thus, it is necessary to think about how to read the link to the file in different ways, and only in Android. This kills all the benefits of Flutter as a cross-platform development tool.

[zoechi]

There won't be a content:// uri on iOS, os is this even relevant, or would it?
You still can wrap different approaches behind a common API in Dart so that the user of a plugin doesn't need to know the difference.
Some special behavior from the underlying platform will always leak through though.

[andyduke]

There is no content uri on iOS, there is an Android only. When you receive a link to a file, you need to check which link it is and write a lot of different code to process it. Since files are a fundamental thing, there will be many such places. Files can be used differently, converted from JSON, passed to the Image class, used when calling other libraries. It’s not always possible to do processing, for example, it’s difficult to pass such a link to the Image class.

Therefore, I think it would be correct to hide this Android feature inside the base classes for working with files, otherwise they are not needed at all (since they do not perform their task), let everyone write their own file plug-ins for all platforms - now it looks exactly like that. And it is all the more strange since Flutter and Dart are developed by Google, but for Android you need to use a dirty workaround.

[agnoam]

Someone has made this plugin ?