-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[firebase_storage] StorageUploadTask's event stream is never closed #2141
Comments
Same!!! |
Hi @jenshor |
I added the parts of the |
Hi @jenshor |
Alright. Attached the logfile to the post. |
I have similar kind of issue when using firebase_storage Thanks in advance |
Hey @jenshor, given the amount of change to |
Hey @jenshor. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Given the rework #3612 and lack of response, I'm going to assume this isn't an issue anymore. Will reopen if this is not the case. |
Describe the bug
The stream of the
StorageUploadTask
'sevents
property is not closed; Therefore, awaitingevents.last
will never return.To Reproduce
Code for reproduction:
Expected behavior
The stream is properly closed when the file is successfully uploaded.
Additional context
I dug a bit into the code of the StorageUploadTask implementation and it seems that the
StreamController<StorageTaskEvent> _controller
is never closed. Therefore, I changed the implementation locally on my system by closing_controller
when aStorageTaskEvent
with aStorageTaskEventType
ofStorageTaskEventType.success
occurred. Closing the controller had the effect that theawait events.last;
call returned the moment the file was successfully uploaded. I think the described fix might be related to #1314flutter doctor -v:
pubspec.yaml
Log
flutterRunLogFile.txt
The text was updated successfully, but these errors were encountered: