-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[Proposal][WIP] Storage improvements #1260
Comments
The issues linked above (except multiple bucket support) have live fixes now in the v4.3.0 release. New features / adding support for missing features will be done in the v5.x.x release cycle. Loving
|
Guys, multiple storage support has not yet been released? |
@ziyafenn doesn't appear so. I've had to add multiple app instances - one for each bucket. |
Closing in favour of the above-mentioned PR. |
Hi all 👋
storage()
has fallen slightly behind recently and we plan on improving the module for a 5.x.x release which includes improving it to ensure that it provides the all the functionality in an easy to use and reliable manner with better documentation and bug fixes.This issue is a placeholder that will be updated as we have more details on what will be supported and how this will be structured in the API.
Secondly, it's also here to show that we're aware of the issues that have already been raised and will be addressing them as part of this proposal. Any historic or new issues will be closed and redirected here to track all the issues that need addressing in one place.
New features to add:
StorageTask
; and support for resumable uploads/downloadscancel()
resume()
pause()
Loving
react-native-firebase
and the support we provide? Please consider supporting us with any of the below:React Native Firebase
andInvertase
on TwitterThe text was updated successfully, but these errors were encountered: