Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Amplify.Auth.signOut Method Issue #5452

Closed
3 of 14 tasks
bharathiselvan opened this issue Sep 13, 2024 · 6 comments
Closed
3 of 14 tasks

Amplify.Auth.signOut Method Issue #5452

bharathiselvan opened this issue Sep 13, 2024 · 6 comments
Labels
to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided

Comments

@bharathiselvan
Copy link

Description

The Amplify.Auth.signOut method is not logging the user out completely. When attempting to log in again using Amplify.Auth.signInWithWebUI, the Hosted UI allows the previously signed-out account to log in without requiring re-authentication.

Categories

  • Analytics
  • API (REST)
  • API (GraphQL)
  • Auth
  • Authenticator
  • DataStore
  • Notifications (Push)
  • Storage

Steps to Reproduce

Sign in using Amplify.Auth.signInWithWebUI.
Call Amplify.Auth.signOut to log out the user.
Attempt to log in again using Amplify.Auth.signInWithWebUI.
Observe that the Hosted UI allows the previously signed-out account to log in without prompting for re-authentication.

Screenshots

No response

Platforms

  • iOS
  • Android
  • Web
  • macOS
  • Windows
  • Linux

Flutter Version

3.19.1

Amplify Flutter Version

1.6.1

Deployment Method

Amplify Gen 2

Schema

No response
@github-actions github-actions bot added pending-triage This issue is in the backlog of issues to triage pending-maintainer-response Pending response from a maintainer of this repository labels Sep 13, 2024
@mahesh87ta
Copy link

I also encounter same issue.

@GitHub-user-Bala
Copy link

I’m also encountering the same challenge.

@tyllark
Copy link
Member

tyllark commented Sep 13, 2024

Hi @bharathiselvan, thank you for submitting this issue. We will take a look at this issue and get back to you when we have any updates or questions.

@github-actions github-actions bot removed the pending-maintainer-response Pending response from a maintainer of this repository label Sep 13, 2024
@Equartey Equartey added the to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided label Sep 16, 2024
@Equartey
Copy link
Contributor

Hi @bharathiselvan, this sounds like a duplicate of #4747 (comment). Does this comment address the what you're seeing?

@Equartey Equartey added the pending-community-response Pending response from the issue opener or other community members label Sep 16, 2024
@Equartey
Copy link
Contributor

@bharathiselvan Ah, I see your comment on the feature request: #1528.

This feature request is still in our backlog and besides the comment I linked above, we do not have any other guidance at this time.

I'm going to close this issue as a duplicate.

@Equartey Equartey closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2024
@github-actions github-actions bot removed pending-community-response Pending response from the issue opener or other community members pending-triage This issue is in the backlog of issues to triage labels Sep 16, 2024
@github-actions GitHub Actions
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Equartey @bharathiselvan @mahesh87ta @tyllark @GitHub-user-Bala