Migration from 2.0.x to 2.1.x
This guide contains instructions for migration from Mobile Token JS SDK version 2.0.x
to version 2.1.x
.
Changes in WMTPush
API
The WMTPush
API has been updated to provide a more structured way of creating push platform instances. The following changes have been made:
register
method now accepts aWMTPushData
instance instead of individual parameters.- New static methods for creating
WMTPushData
instances for different push services have been added:WMTPushData.apns(token: string, environment?: WMTAPNSEnvironment, supportLegacyServer: boolean)
for Apple Push Notification Service (APNs).WMTPushData.fcm(token: string, supportLegacyServer: boolean)
for Firebase Cloud Messaging (FCM).WMTPushData.hms(token: string, supportLegacyServer: boolean)
for Huawei Mobile Services (HMS).
- The
supportLegacyServer
parameter is now a part of theWMTPushData
class, allowing you to specify if the platform should support legacy push registration (1.9 or earlier versions of the Wultra Mobile Token API).
Last updated on Aug 26, 2025 (08:46)
Edit on Github
Send Feedback