You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue found in Native App or Hybrid App: Hybrid (custom build)
OS Version: 17.0.1
Device: iPhone 13 Max
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.
Actual behavior: App is left in an uncertain state
Expected Behavior: User list should not be cancelable (or swipable) when there is no current user
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.
The text was updated successfully, but these errors were encountered:
Please fill out the following details:
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:
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.
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.
The text was updated successfully, but these errors were encountered: