Vivox Unity SDK 16.13.0

Key features and bugs addressed

1. Feature

   Added

2. Feature

   Added `VivoxConfigurationOptions.TextToSpeechEngine` to select the text-to-speech engine, and `VivoxService.Instance.TextToSpeechEngine` to read the engine in use. `TextToSpeechEngine.Native` uses the operating system's voices and languages on macOS, iOS, tvOS, Android, and Windows 10 and later desktop, and requires Vivox Core 5.29 or later. On platforms and OS versions without a native engine, selecting `Native` logs a warning and uses the built-in engine.

   • Windows
   • macOS
   • Android
   • iOS
3. Fix

   Fixed

4. Fix

   Fixed the package failing to import, and IDEs reporting the Vivox assembly as missing, in Windows projects whose path is longer than about 100 characters. The longest generated file name is now 60 characters instead of 78, so projects can use paths of up to about 120 characters before reaching the Windows 260-character limit.

   • Windows
5. Fix

   Fixed `LeaveChannelAsync` , `LeaveAllChannelsAsync` , `StopAudioInjection` , `TextToSpeechCancelAllMessages` and `TextToSpeechCancelMessages` signing the player back in when called while signed out. When the Authentication package isn't used, that sign-in created a session under a new random player ID instead of the `LoginOptions.PlayerId` the application had signed in with, and nothing signed it out. These calls now do nothing while signed out. They still wait for a sign-in that is already in progress.

6. Fix

   Fixed directed messages sent by the signed-in player not being delivered back to that player. Channel messages were already raised to their sender, but directed messages were not, so a player's own directed messages did not appear in the conversation until chat history was re-requested. They are now raised through `DirectedMessageReceived` like channel messages, carrying the server-assigned `MessageId` that is required to later edit or delete them. Check `VivoxMessage.FromSelf` to distinguish your own messages from those received from other players.

7. Change

   Changed

8. Change

   When a Vivox API signs the player in implicitly without the Authentication package, a warning is now logged with the generated player ID.

9. Change

   `VivoxMessage.RecipientPlayerId` is now also populated on directed messages raised back to the player who sent them, where previously it was populated only for messages returned by `GetDirectTextMessageHistoryAsync` . It identifies the conversation a message belongs to, which `SenderPlayerId` cannot do on those messages because it is the signed-in player.

10. Change

    Upgraded the underlying Vivox Core SDK to version `5.29.0` .

11. Removal

    Removed

12. Removal

    Removed support for the 32-bit ARM (ARMv7) architecture on Universal Windows Platform. ARM64, x64 and x86 remain supported.

    • Windows