1Table of Contents 2 2Copyright Notice 2 3Document Version and Release Date 3
Download 41.59 Kb.
|
- Navigate this page:
- 3Document Version and Release Date
- 4.2Compatible Client Device/OS
- 4.3Compatible SPiDR Server Versions
- 5SPiDR MobileSDK iOS and Android Changes
- 5.1.4Details on Solved Issues Needing Further Explanation
|
Release Notes SPiDR MobileSDK 4.2.5 1Table of Contents1Table of Contents 2 2Copyright Notice 2 3Document Version and Release Date 3 4Introduction 3 4.1Feature List 3 4.2Compatible Client Device/OS 3 4.3Compatible SPiDR Server Versions 4 5SPiDR MobileSDK iOS and Android Changes 4 5.1API Changes 4 5.1.1iOS API Changes 4 5.1.2Android API Changes 4 5.1.3Solved Issues 4 5.1.4Details on Solved Issues Needing Further Explanation 6 5.1.5Known Issues and Limitations N/A 6
6.1.1iOS Transition 7 6.1.2Android Transition 7
2Copyright NoticeCopyright - 2016 GENBAND. All rights reserved. The information in this document is proprietary to GENBAND. Except as specifically authorized in writing by GENBAND, the holder of this document shall keep the information contained herein confidential and shall protect it in whole or in part from disclosure and dissemination to third parties and use it for evaluation, operation, and maintenance purposes only. Changes or modifications to this Release Notes document without the express consent of GENBAND may void the user's warranty and/or authorization to operate the equipment. Information in this document is subject to change without notice. GENBAND reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. GENBAND, and the GENBAND logo, are trademarks of GENBAND. All other brands, names, or trademarks mentioned in this document are the property of their respective owners. 3Document Version and Release DateMobileSDK 4.2.5 GA Release Date: 05.12.2016
4IntroductionThis document provides a simple introduction to the SPiDR MobileSDK 4.2.5 software and known key software limitations. This document contains crucial information and should be read before starting the upgrade to or installation of SPiDR MobileSDK 4.2.5 4.1Feature ListThe following features were introduced in SPiDR MobileSDK 4.2.5 Release:
WebRTC is upgraded to Android webrtc_revision= 57c1ad3b16b222d5e63bf94d96a32c652e2e59d8 4.2Compatible Client Device/OS
4.3Compatible SPiDR Server Versions
5SPiDR MobileSDK iOS and Android Changes5.1API Changes5.1.1iOS API ChangesNo API change was added within MobileSDK 4.2.5. 5.1.2Android API ChangesNo API change was added within MobileSDK 4.2.5. 5.1.3Solved Issues
Description: 1. change wifi1 -> wifi2 - OK 2. change wifi2 -> wifi1 - OK 3. move to air plane mode and back (3 sec on airplane mode) call is ended on iOS Expected result: Call must not be ended. Workaround: None.
Description: Steps:
2. B rings & answers. A & B are connected in a video call. 3. A & B are in video call for 10 minutes. Observe "Computed power usage" offsets number again. 4. A & B can tap on the icon next to the "End call" icon to switch to Rear camera, then tap on that icon again to switch back to Front camera. Actual result: After 1 minute of video call, it gets disconnected automatically at B side (B party disconnect the call automatically) Expected result: Call must not be disconnected. Workaround: None.
Description: Steps:
Expected result: App must not crashed. Workaround: None.
Description: Screen share functionality causes crash Expected result: Crash must not be observed. Workaround: None
Description: Crash is observed. There is no specific scenario. Expected result: Crash must not be observed. Workaround: None
Description: A calls B on video call, B enable the video, App crashes on A side and then B side (Huawei device) is not responding and eventually crashes. Expected result: Crash must not be observed. Workaround: None
Description: A calls B on a video call B clicks to enable the video The Gionee device crashes, Whether it is A party or B party. Expected result: Crash must not be observed. Workaround: None
Description: User A call to user B video call User A and B stop and begin the video many times User A hanged the call The app on user A is crashed Expected result: Crash must not be observed. Workaround: None 5.1.4Details on Solved Issues Needing Further ExplanationN/A
5.1.5Known Issues and Limitations
|