The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.
**Version 5.6.3 Release Notes:**
- It has been determined that the voice call was not opened properly after the APNS push call notification for the first voice call and it has been fixed.
- The problem of sound coming out of the speaker when incoming voice calls are opened has been fixed. Unlike video calls, audio calls will not be send to speaker and the users can be send audio to speakers if they wish.
**Version 5.6.3**
**Release Notes**
- The problem of adding the port number when path is included in the Server Websocket Endpoint address has been fixed.
**Version 5.6.2**
**Release Notes :**
The following problems detected with TrigerAppMessage which developed in Version 5.5.0 have been corrected.
- It was observed that the subscribeToTriggerAppEvent method subscribed to the NeedToLoginEvent, that is, it connected to a wrong event, and it was corrected.
- With TrigerAppMessage, the entire content of such messages was made visible in the dialog list. In other words, instead of showing these types of messages on a single line with the end of the message content trimmed, a change was made to show the entire message content. After this change, there was a problem in the display of missed video call texts and it was fixed with this version.
In applications using DiyalogSDK compiled with Xcode 15.* and later, due to a behavior change by Apple at the operating system level (IOS 17), it was observed that the SDK received an exception while listing retrospective chat messages, and necessary precautions were taken regarding this situation.
**Version 5.6.1**
**Release Notes :**
The following problems detected with TrigerAppMessage which developed in Version 5.5.0 have been corrected.
- It was observed that the subscribeToTriggerAppEvent method subscribed to the NeedToLoginEvent, that is, it connected to a wrong event, and it was corrected.
- With TrigerAppMessage, the entire content of such messages was made visible in the dialog list. In other words, instead of showing these types of messages on a single line with the end of the message content trimmed, a change was made to show the entire message content. After this change, there was a problem in the display of missed video call texts and it was fixed with this version.
- In applications using DiyalogSDK compiled with Xcode 5.3 and later, due to a behavior change by Apple at the operating system level (IOS 17), it was observed that the SDK received an exception while listing retrospective chat messages, and necessary precautions were taken regarding this situation.
**Important note :**
In version 5.6.0 and later, it is mandatory to configure the server trusted keys in your application as follows before calling the createDialog method. If this is not done, DiyalogSDK will not be able to establish a connection with its own server.
`DiyalogEngine.diyalogInstance().trustedKeys = [“<your public key-01>“,
“<your public key-02>“,
“<your public key-03>“,
“<your public key-04>“,
“<your public key-05>“ ]`
Diyalog versiyon 5.6.0
Version 5.6.0 Release Notes:
- Even though SSL pinning is not required, SSL pinning was added upon request from some of our customers. For SSL pinning, it will be sufficient to transmit the SSL public key fingerprint of your Diyalog endpoint server to Diyalog SDK before calling the createDiyalog function as follows.
```
let yourSSLPublicKeyHash = “<Base64 encoded your endpoint public key fingerprint>“;
DiyalogEngine.diyalogInstance().setPinnedCertificates([yourSSLPublicKeyHash])
```
- Diyalog platform is no longer allowed to run with default server public keys for communication security. If this new version SDK will be used, the public keys of the Diyalog server installed in its datacenter should be given to the SDK as follows and then the createDiyalog function should be called.
```
DiyalogEngine.diyalogInstance().trustedKeys = [“<your public key-01>“,
“<your public key-02>“,
“<your public key-03>“,
“<your public key-04>“,
“<your public key-05>“ ]
```
**Important Note**: If keys is not set after using DiyalogSDK Version 5.6.0, it will not be able to connect to the Diyalog SDK server and perform its functions. For this reason, trustedKeys must be set to the SDK after version 5.6.0.
- The resetDiyalogConnection function has been added to the SDK in order to connect to two different institutions with DiyalogSDK within the same application and perform Video Help without any problems.
After the Diyalog parameters (endpoint, trsutedKeys, ssl ping fingerprint, etc.) given for the relevant institution are set, this new method should be called before calling the new createDialog function.
`
DiyalogEngine.diyalogInstance().resetDiyalogConnection()
`
- A new message type of TriggerAppMessage type has been added. These messages can be processed and displayed. With this message type, it is possible to transmit commands and data from backoffice applications to the main application. When the user clicks on this message on the frontend, the command and data in the message are transmitted to the main application through the TriggerAppEvent listener.
- The ability to share files and images in live support chat operations has now been enabled through the main application.
The default value is set to false, meaning file and image sharing is disabled. To open it, it can be activated while creating the Dialog as follows.
DiyalogEngine.diyalogInstance().setOnlineHelpAttachmentEnabled(true)
- In customer acquisition and video call with representative support transactions, the internet connection type of the customer phone is reflected on the representative screens.
- In iOS clients, texts such as call ended or missed call are written in English in the notifications, even if the application language is Turkish. Necessary arrangements have been made for writing in Turkish.
- The voice message sending button has been made easier to use in IOS clients.
- Customers can share files and images in live support chat transactions.
- In iOS clients, the automatic call start structure when the video call push is clicked has been changed and the call screen is displayed after clicking the push, allowing the customer to hang up the call if he/she wishes.
- A transparent black background has been added behind the buttons to increase the visibility of the buttons in video calls when the other party's image is white.
- To prevent customers from accidentally exiting the Live Help chat screens, click "Do you want to end the session?" Approval has started to be received with a warning.
- In iOS clients, texts such as call ended or missed call are written in English in the notifications, even if the application language is Turkish. Necessary arrangements have been made for writing in Turkish.
- The voice message sending button has been made easier to use in IOS clients.
- Customers can share files and images in live support chat transactions.
- In iOS clients, the automatic call start structure when the video call push is clicked has been changed and the call screen is displayed after clicking the push, allowing the customer to hang up the call if he/she wishes.
- A transparent black background has been added behind the buttons to increase the visibility of the buttons in video calls when the other party's image is white.
- To prevent customers from accidentally exiting the Live Help chat screens, click "Do you want to end the conversation?" Approval has started to be received with a warning.
Version 5.2.0
- When the application is restored from the backup, enabling or not re-enabling the Dialog users can be set via the SDK configuration.
It can be configured by following code. Default is restoring from backup is enabled.
DiyalogEngine.diyalogInstance().setEnableUserBackup(false)
- Encreypted OTP push notification messages cannot be decrypted in some exceptional cases. And users is seeing encrtypted message content. "You have new message" content will display to users in notification, if there is an exception after this version of sdk.
- Some crash cases are fixed.
zoomfactor settings added for Turkish id cards in backcamera for iphone 14 pro and iphone 14 pro max devices