fix(passport): no window opener#2629
Closed
nattb8 wants to merge 12 commits into
Closed
Conversation
34c216a to
3ce7f22
Compare
3ce7f22 to
1c069e4
Compare
|
View your CI Pipeline Execution ↗ for commit a631f67.
☁️ Nx Cloud last updated this comment at |
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
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.
Hi👋, please ensure the PR title follows the below standards:
type(scope): message. For example:feat(passport): my new feature!after thetype(scope), for examplefeat(passport)!: my new breaking featureContext
ID-3722
Facebook login in Play is currently broken - users get stuck on the "Welcome, you're logged in" page and aren't redirected back to the app. This doesn't affect Google, Apple, or email login. The issue has been reproduced in the Passport sample app and is caused by a
No window.opener. Can't complete notification.error during the callback.A fix has been merged into the
mainbranch ofoidc-client-ts, but it hasn't been included in an official release. Since their release schedule is irregular, we’re applying a temporary workaround to unblock affected teams.Detail and impact of the change
Changed
Temporarily updated our TS SDK to depend on the
mainbranch ofoidc-client-tsto include the fix.Anything else worth calling out?
This will be published as an alpha release to unblock teams affected by the Facebook login issue.
Once
oidc-client-tspublishes an official release with the fix, we'll update our dependency accordingly and release a stable SDK version.