StorageReference instead of Location about firebase_image HOT 3 OPEN

(getBucket is not going to yield the location.) I've taken a closer look at the Firebase Storage API and am truly surprised that one can translate a Url to a StorageReference, but not the other way around -- at least easily.

At the application level, using fully qualified Urls for Firebase Storage is problematic if you want to be able to export/import between databases. Hence, I store relative paths and use StorageReference.child to compute the correct image location... Alas, getting that into a location string requires TWO ASYNC calls. 🤦‍♂️

from firebase_image.

I managed to get this working fairly well. I reluctantly wrapped a FutureBuilder around the FadeInImage, but since it shows the BlurHash placeholder (same as FadeInImage), it does not create the jank that I was initially worried about.

I still think Firebase Storage needs to improve their API. I opened an issue for them, but I'm not holding my breathe. If they improve their API, I can improve my code.

I still think there is room to revise FirebaseImage to be more StorageReference centric rather than String centric.

from firebase_image.

You can give storage reference of folder too.
This is how..
Future downloadFile(String duaName) async {
final Directory tempDir = Directory.systemTemp;
final File file = File('${tempDir.path}/$duaName');
final StorageReference ref = FirebaseStorage.instance.ref().child('FileType.image/').child('$duaName');
String url = await ref.getDownloadURL();
final http.Response downloadData = await http.get(url);
var bodyBytes = downloadData.bodyBytes;

 _scaffoldKey.currentState.showSnackBar(
  SnackBar(
    backgroundColor: Colors.white,
    content: Image.memory(
      bodyBytes,
      fit: BoxFit.fill,
    ),
  ),
);

final StorageFileDownloadTask downloadTask = ref.writeToFile(file);
print(downloadTask.toString());

return url;
}

Hope this is helpful for you.

from firebase_image.