Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[firebase_storage] default or empty paths are not handled #1505

Closed
kroikie opened this issue Nov 28, 2019 · 0 comments
Closed

[firebase_storage] default or empty paths are not handled #1505

kroikie opened this issue Nov 28, 2019 · 0 comments
Labels
impact: customer A bug with low impact (e.g. affecting only a few customers or has a workaround). (P3) plugin: storage type: bug Something isn't working

Comments

@kroikie
Copy link
Collaborator

kroikie commented Nov 28, 2019

Describe the bug
The plugin currently expects references to have an additional path. If the default bucket is used then no/empty path is submitted. Using .child(path) on a reference with an empty path results in a PlatformException. The plugin should check for the path before calling .child(path) on a reference.

To Reproduce
Steps to reproduce the behavior:

  1. Get the metadata of the default storage bucket.

Expected behavior
Return metadata
@kroikie kroikie added the type: bug Something isn't working label Nov 28, 2019
@kirstywilliams kirstywilliams added impact: customer A bug with low impact (e.g. affecting only a few customers or has a workaround). (P3) plugin: storage labels Apr 27, 2020
@Salakar Salakar mentioned this issue Sep 22, 2020
Merged
22 tasks
@Salakar Salakar closed this as completed Apr 1, 2021
@firebase firebase locked and limited conversation to collaborators May 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
impact: customer A bug with low impact (e.g. affecting only a few customers or has a workaround). (P3) plugin: storage type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kirstywilliams @kroikie @Salakar