Open
Conversation
Pull Request Test Coverage Report for Build 21251112215Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
The flutter_secure_storage_web 1.2.1 dependency (from flutter_facebook_auth) uses deprecated web APIs (dart:html, dart:js_util) that are incompatible with Flutter's WASM compilation. This commit adds dependency overrides for the flutter_secure_storage package and its platform implementations to use newer versions that support the modern web APIs (dart:js_interop). Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Feature / example update
What is the current behavior?
The Supabase Flutter example only shows email/password auth and does not include a Facebook SDK login flow.
What is the new behavior?
Adds a Facebook SDK sign-in flow to the example using , plus platform setup for Android and iOS and README setup guidance.
Additional context
Facebook App ID/client token and Supabase URL/keys remain placeholders for local configuration.