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

Fix keeping wrong interactor state after CV engagement #1168

Conversation

EgorovEI
Copy link
Contributor

MOB-3901

What was solved?
After having CV engagement if visitor starts Live engagement, SDK immediately shows Engagement Ended dialog.
This PR fixes this behaviour.

Release notes:

  • Feature
  • Ignore
  • Release notes (Is it clear from the description here?)
  • Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

  • Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
  • Did you add logging beneficial for troubleshooting of customer issues?
  • Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from iOS SDKsThings to consider for newly added logs in Confluence for more information.

@EgorovEI EgorovEI merged commit 22ff2eb into feature/entry-widget-and-secure-conversations-v2 Dec 23, 2024
8 checks passed
@EgorovEI EgorovEI deleted the bug/MOB-3901-call-visulizer-breaks-live-engagement-flow branch December 23, 2024 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants