Skip to content

fix(storage, web): fixed web stream handlers, e2e web tests, incorrect NativeError being thrown instead of FirebaseException on web #12319

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

Merged
merged 18 commits into from
Feb 14, 2024

Conversation

russellwheatley
Copy link
Member

@russellwheatley russellwheatley commented Feb 12, 2024

Description

Changes to Web

  • Fixed the NativeError exception in flutterfire internals that was a problem across all plugin web exceptions.
  • Fixed the stream handling on Storage web that was propagating two exceptions when they occurred.
  • Fixed stream handling on Storage web to ensure onDone is called when finished either successfully or when there is an error.
  • Updated e2e tests to ensure no I/O operations occur when running storage web e2e tests.
  • Added more tests around snapshotEvents to ensure it was properly closed and calling onDone method.
  • Renamed flutter.dart to reference_web.dart as it should be.

Related Issues

Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

@russellwheatley russellwheatley changed the title fix(storage, web): fix stream handlers, e2e tests and the incorrect NativeError being thrown instead of FirebaseException fix(storage): fix stream handlers, e2e tests, incorrect NativeError being thrown instead of FirebaseException on web, cancel() on apple Feb 13, 2024
@russellwheatley russellwheatley changed the title fix(storage): fix stream handlers, e2e tests, incorrect NativeError being thrown instead of FirebaseException on web, cancel() on apple fix(storage): fix stream handlers, e2e tests, incorrect NativeError being thrown instead of FirebaseException on web, task.cancel() on apple Feb 13, 2024
@russellwheatley russellwheatley changed the title fix(storage): fix stream handlers, e2e tests, incorrect NativeError being thrown instead of FirebaseException on web, task.cancel() on apple fix(storage): fixed web stream handlers, e2e web tests, incorrect NativeError being thrown instead of FirebaseException on web, task.cancel() on apple Feb 13, 2024
@russellwheatley russellwheatley changed the title fix(storage): fixed web stream handlers, e2e web tests, incorrect NativeError being thrown instead of FirebaseException on web, task.cancel() on apple fix(storage): fixed web stream handlers, e2e web tests, incorrect NativeError being thrown instead of FirebaseException on web Feb 13, 2024
@russellwheatley russellwheatley changed the title fix(storage): fixed web stream handlers, e2e web tests, incorrect NativeError being thrown instead of FirebaseException on web fix(storage, web): fixed web stream handlers, e2e web tests, incorrect NativeError being thrown instead of FirebaseException on web Feb 13, 2024
return exception is core_interop.FirebaseError;
bool _testException(Object? objectException) {
final exception = objectException! as core_interop.JSError;
// ignore: unnecessary_cast
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the cast?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The analyser was causing a warning if the cast isn't there. Not entirely sure why but might be something to do with the shimmer for all platforms.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants