v1.19.0

Features

• [DX-2974] Use GetLinkedAddresses to retrieve the list of external wallets linked to a user's Passport account via the Dashboard. (#222)

v1.18.0

Chores

• [DX-2964] Updated the game bridge (built from the Typescript SDK version 1.44.3) (#220)

v1.17.0

Fixes

• [DX-2959] Resolved an issue where the SDK did not throw an error if the provider was not set when connecting to IMX and EVM. Customers should update to ensure proper connection handling. (#218)

v1.16.6

Features

• [DX-2863] Customers can now use ZkEvmSendTransactionWithConfirmation to both send a transaction and obtain its final status in a single function call, removing the need for ZkEvmGetTransactionReceipt. (#194)

v1.15.0

Features

• [DX-2809] Customers can now properly logout using the Unity SDK instead of the previous version, where logout wasn't working correctly. (#192)

Documentation

• [DX-2784] Updated documentation and sample code for TransactionReceiptResponse status field now makes it easy to understand transaction status response while calling ZkEvmGetTransactionReceipt.

Chores

• Improve the contribution guide section in README (#189)

v1.14.0

Features

• [DX-2784] Customers can use ZkEvmGetTransactionReceipt to retrieve transaction information of a given transaction hash. The TransactionReceiptResponse.cs file contains the full response data model. (#185)

Fixes

• [DX-2793] Customers using older Unity versions can now integrate the SDK without encountering nullability errors. (#186)

v1.13.0

Features

• [DX-2771] Allows customers to run Windows-based games both within the editor and as a game build simultaneously. (#183)

v1.12.0

Fixes

• [DX-2753] When starting the SDK, some Windows users may experience the engine start-up timeout issue. Added Volstro's fixes to attempt to resolve the timeout issue. (#180)
• Added Unity.InputSystem reference back to Volstro UnityWebBrowser

v1.10.0

Features

• [DX-2756] Added get Passport ID function so customers no longer need to decode it from the access or ID token. (#179)

v1.9.0

Fixes

• [DX-2757] Some Android devices and newer Android versions may prevent customers from logging in using the PKCE flow. This is due to how the SDK handles Chrome Custom Tabs dismissal. To solve this, the SDK now detects how Chrome Custom Tabs were dismissed differently. (#178)