flutter_cache_manager
flutter_cache_manager copied to clipboard
Fix bucket name being reused between instances of different buckets
:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
This fixes an issue in which a subsequent FirebaseCacheManager instance cannot load or upload files correctly because the bucket name was set and cached in the first FirebaseCacheManager instance. It also updates packages to latest versions.
:arrow_heading_down: What is the current behavior?
In my case when I try to read a file from another bucket I see error " [firebase_storage/object-not-found] No object exists at the desired reference." although the file is there.
:new: What is the new behavior (if this is a feature change)?
If we're initializing a FirebaseCacheManager with a new instance, it makes sure to use another cache key so that files from the other bucket can be read.
:boom: Does this PR introduce a breaking change?
No
:bug: Recommendations for testing
Hmm, not sure
:memo: Links to relevant issues/docs
:thinking: Checklist before submitting
- [ ] All projects build
- [ ] Follows style guide lines (code style guide)
- [ ] Relevant documentation was updated
- [ ] Rebased onto current develop