Releases: zumo/zumokit-react-native
Releases · zumo/zumokit-react-native
Release list
ZumoKit 4.9.0
Improved recovery process
ZumoKit 4.8.11
Release 4.7.0
Add direct custody deposit support:
- Expose direct deposit address on custody accounts
- Allow to override destination user when submitting direct custody deposit transaction
Release 4.6.2
Release 4.6.0
Custody Order now exposes these additional props:
/** Debit account's user identifier, if applicable. */
fromUserId: string | null;
/** Debit account's user integrator identifier, if applicable. */
fromUserIntegratorId: string | null;
/** Credit account's user identifier, if applicable. */
toUserId: string | null;
/** Credit account's user integrator identifier, if applicable. */
toUserIntegratorId: string | null;Release 4.5.1
- Custody service URL is now required ZumoKit SDK constructor param
- Rework Custody Withdraw flows to get estimated fees from Custody Service
- Custody Withdraw is now a two step process, where first custody order is created and then executed
- Custody Order now exposes these additional props:
/** Custody order amount, null if not known yet. */
amount: Decimal | null;
/** Flag indicating if fees are included in order amount. */
feeInAmount: boolean;
/** Estimated custody order fees. */
estimatedFees: Decimal | null;
/** Actual custody order fees, null if not known yet. */
fees: Decimal | null;Release 4.4.1
Bugfix: fix crash when submitting exchange on Android
Release 4.4.0
Release 4.3.3-alpha.1
Bugfixes: Fixes following issues with transaction.custodyOrder properties:
- updatedAt and createdAt both null
- status was lowercase instead of uppercase
- deposits:
- fromAddresses null instead of array of addresses that custody deposit was made from
- toAccountId null instead of id of account that custody deposit was made to
- withdraws:
- fromAccountId null instead of id of account that custody withdraw was made from
- toAddress null instead of address that custody withdraw was made to
Release 4.3.2-alpha.1
Bugfix: Make exchange.debitTransactionId nullable again to avoid SDK crashes in some edge cases