You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears there's a bug with the way the new Compat delegates are setup in storage, a good reproduction is to cancel an upload and then check the snapshot state.
task.snapshot.state still equals running, whereas task._delegate.snapshot.state appropriately reads canceled.
You can see this on success too. I noticed this while debugging AngularFire/RxFire issues that users were reporting, while I worked around this by using the promise for now developers won't be able to takeWhile(snap => snap.state === 'running') etc. to catch errors, leading to broken observables and general mayhem in their apps.
Attached some screenshots of states seen in my console.logs. Note the conflict between the _delegate and the compat states.
The text was updated successfully, but these errors were encountered:
It appears there's a bug with the way the new
Compat
delegates are setup in storage, a good reproduction is to cancel an upload and then check the snapshot state.task.snapshot.state
still equalsrunning
, whereastask._delegate.snapshot.state
appropriately readscanceled
.You can see this on success too. I noticed this while debugging AngularFire/RxFire issues that users were reporting, while I worked around this by using the promise for now developers won't be able to
takeWhile(snap => snap.state === 'running')
etc. to catch errors, leading to broken observables and general mayhem in their apps.Attached some screenshots of states seen in my console.logs. Note the conflict between the _delegate and the compat states.
The text was updated successfully, but these errors were encountered: