v4.3.6

Fixes

• Fixed an issue where the message list did not scroll to the bottom when moving from message replies to messages list. This fix is aimed at improving navigation and message visibility.
• Rectified a multifaceted issue where the application experienced performance issues when User A and User B were on a call and User C attempted to call User B. The fix ensures accurate call status display at User C's end, updates the call status correctly at User B's end when User A ends the call, and prevents the web application from freezing during repeated call attempts. This enhances system performance and reliability.
• Resolved an intermittent issue where the incoming message bubble was not generated in real time in the message list. This fix ensures prompt rendering of incoming messages, thereby improving real-time communication and user experience.
• Addressed an issue where a new incoming call was not automatically rejected with a 'busy' status when a user received a call while they were already engaged in another call. This fix ensures the appropriate 'busy' status is displayed to the caller, maintaining uninterrupted ongoing calls.
• Addressed an issue occurring when User A calls User B and User B rejects the call. The fix corrects the call status display at User A's end to 'reject call' instead of 'missed call', ensures the unread count doesn't incorrectly increase at both ends, and guarantees the 'missed call' message is displayed in real-time, without needing to refresh or fetch again. This fixes improve the accuracy of displays, counts, and real-time updates.
• Addressed an issue where incorrect call messages were displayed when User A, already on a call, received a new call from User C. The fix ensures a 'Call Busy' message is correctly displayed at User C's end instead of 'unanswered call', and a 'missed call' message is accurately shown at User A's end. This change enhances the clarity and accuracy of call status displays.
• Resolved an issue with incorrect call status display in both the message list and the last message in the Conversation List. This fix ensures the accurate depiction of call statuses, enhancing user experience and communication clarity.
• Rectified an issue where the call message was not displayed in real-time when User A called User B and User B didn't pick up. This fix ensures immediate visibility of the call status, enhancing real-time communication and user experience.
• Resolved an issue with call notifications when a user is logged in on multiple devices. This was noticed when User A, logged in on - Device 1 & 2, calls User B and also erroneously receives an incoming call notification on Device 2. The fix also addresses the problem of notification persistence on Device 2, ensuring that it disappears appropriately when the call is canceled, rejected, or accepted. This update enhances the accuracy of call notifications and user experience across multiple devices.
  (edited)