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.

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

User list presented after logging out can be dismissed, leaving app in an uncertain state #3690

Open
mattlacey opened this issue Mar 11, 2024 · 1 comment
Labels

Comments

@mattlacey
Copy link

Please fill out the following details:

  1. Version of Mobile SDK Used: 11.1
  2. Issue found in Native App or Hybrid App: Hybrid (custom build)
  3. OS Version: 17.0.1
  4. Device: iPhone 13 Max
  5. Steps to reproduce:

a. Have multiple users signed in, and sign out as one user.

In our hybrid UI we have a logout button that invokes the following Swift code:

        guard let account = UserAccountManager.shared.currentUserAccount else { return }
        UserAccountManager.shared.logout(account)
        PushNotificationManager.sharedInstance().unregisterForSalesforceNotifications(user: account) { result in }

b. The SDK then presents the user list in response to this
c. Swipe down to dismiss the user list - the app receives no notification that this has happened, but there is now no current user.

  1. Actual behavior: App is left in an uncertain state
  2. Expected Behavior: User list should not be cancelable (or swipable) when there is no current user
  3. Error Log: None

Further context: We use a custom user list most of the time, and in there it was reasonably trivial to prevent it being swiped away when there is no current user. I now ensure that's visible right after calling the logout code above - but the user list in the mobile SDK should probably do something similar and not allow it to be cancelled when there is no current user.

@bbirman
Copy link
Member

bbirman commented Mar 12, 2024

@mattlacey, thanks for reporting, adding a bug to our backlog

@bbirman bbirman added the bug label Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants