Monday, March 21, 2022
1 change · master
Resolved issues and error corrections
This fixes an internal inconsistency in how live chat or call session records are identified. It helps prevent unnecessary change detection and keeps messaging session data more reliable without changing the user experience.
Original PR description
Before this commit, mismatching types between String and Number would cause inserts to register a change. `rtc.js` used `rtcSession.peerToken`(String) and `rtcSession.id`(number) interchangeably, this commit fixes this issue by favoring the usage of `rtcSession.id`.