Changes for page 5. Changelog

Last modified by teamwire001 on 2024/12/10 07:34

From version 5.9
edited by teamwire001
on 2022/04/28 12:46
Change comment: added notice to 4.14.0
To version 5.7
edited by teamwire001
on 2022/03/07 11:06
Change comment: added 4.13.0

Summary

Details

Page properties
Content
... ... @@ -1,38 +1,6 @@
1 1  = (% class="mark" %)API 16(%%) =
2 2  
3 3  
4 -== 4.14.0 ==
5 -
6 -(% class="lead" %)
7 -Apr 28, 2022
8 -
9 -[[Download IPA file (AdHoc build)>>https://app.box.com/s/w6zi99x0sh58g125ngh4ln2kjlhbfnph||rel="noopener noreferrer" target="_blank"]]
10 -
11 -We have added a new provisioning profile to Teamwire in order to allow screen-sharing during VoIP calls. This means, customers and partners re-signing the Teamwire app, will have to consider the new provisioning profile with the Broadcast Extension App ID. For more information, please refer to the [[updated "Resign App for iOS" document (Registration required).>>doc:Customer.Administration.Resign-App-for-iOS.WebHome]]
12 -
13 -**FEATURES AND CHANGES**
14 -
15 -* **Voice and video group calls**
16 -You can have voice and video calls in group chats with several users. This feature must be enabled by your admin.
17 -* Added the option to share your screen during calls
18 -* Sign-in procedure has been redesigned to improve your onboarding experience
19 -* Added support for locations and attention messages in Federated chats
20 -* If you have failed to enter the correct access code 3 times, Teamwire will now automatically close the session and prompt to sign in again
21 -* We extended our client log to improve future debugging between apps and backend
22 -* Added "Delete account" option in your profile information
23 -
24 -**FIXES**
25 -
26 -* AirWatch would not ask for credentials after force closing the Teamwire app
27 -* On Push-to-Talk, the record button was shown as available while the device’s settings were set to not allow access to microphone
28 -* If the user receives a new reaction notification while the activity panel is open, the messages were in the wrong order
29 -* Under certain circumstances, you'd receive an error message when re-opening Teamwire on managed devices
30 -* Sometimes other user profiles were not updated properly
31 -* Messages from deleted/inactive users were discarded
32 -* Minor UI fixes
33 -
34 -----
35 -
36 36  == 4.13.0 ==
37 37  
38 38  (% class="lead" %)