-
Notifications
You must be signed in to change notification settings - Fork 1
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 engagement started on the chat screen #1194
Fix engagement started on the chat screen #1194
Conversation
08c9ae4
to
8e928ad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice solution 👍
8e928ad
to
0eb5075
Compare
ae3c8f4
to
274f4c5
Compare
@AndriiHorishniiMOC, could you please rebase this branch? |
- Migrate Call and Chat Activities to Kotlin - Refactor CallConfiguration - Refactor EngagementConfiguration MOB 3587
- Moved all the Intent-related functionality to the IntentHelper class. - Abstraction will let us to easily mock this layer. MOB 3582
- Create ActivityLauncher - Rename FilePreview... classes to ImagePreview... MOB 3589
- Create interfaces for EngagementLauncher - Create basic ConfigurationManager that should hold all the init config MOB 3588
This custom attributes can be setup by integrators in their theme.xml
This is needed so that customise glia theme settings in integrators theme.xml
- Remove all the configurations in favor of ConfigurationManager - Get rid of configurations passed through Activity extras - Move extra keys to internal class - Make activities internal - Minor refactoring
Texts have changed, updating according to the Figma designs. MOB-3615
…idget Setup queues each time get Entry Widget is called MOB-3408
…g to design MOB-3478
Side effect of making the layout flat is that now those buttons have slight animation. MOB-3844
Last Core SDK staging build got expired/deleted so uploaded new build
- Added inputDisabled Json to UI remote theme configurations - Switched simple color/drawables to ColorStateList/DrawableStateList MOB-3855
Remove SecureFileAttachmentRepository and some SC use cases that duplicated the logic. Refactor FileAttachmentRepository and the file upload use cases. FileAttachmentRepository is used for both SC and Live Engagement. MOB-3791
Issue introduced in #1183
Do not start a timer for marking messages as read if the leave secure conversation dialog is shown. MOB-3833
…type or starts a new engagement during queueing MOB-3886
2ca729a
to
35d6916
Compare
When the chat screen opens with the secure conversation state, resubscribe to the engagement streams. This solves the upgrade to chat state issue. MOB-3888
0eb5075
to
555bca8
Compare
@DavDo I've rebased it ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -258,6 +259,10 @@ internal class ChatController( | |||
emitViewState { chatState.initChat().setSecureMessagingState() } | |||
ensureSecureMessagingAvailable() | |||
observeTopBannerUseCase() | |||
|
|||
// When the chat screen opens with the secure conversation state, resubscribe to the engagement streams. | |||
// This solves the upgrade to chat state issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also add a Jira bug ticket number here. In case someone in the future decides to refactor any related code so that they have reference to find initial steps to make sure that issue didn't re-surface
ea158b2
to
705f15e
Compare
Closing because this was fixed in #1210, and our principle is to decide the chat state before opening the screen. |
Jira issue:
https://glia.atlassian.net/browse/MOB-3888
What was solved?
When the chat screen opens with the secure conversation state, resubscribe to the engagement streams. This solves the upgrade to chat state issue.
Release notes:
Additional info:
Screenshots: