-
Notifications
You must be signed in to change notification settings - Fork 20
FAQ
- Which version of the iOS platform is supported by the SDK?
- Which version of the SDK do we support?
- Can the Emarsys Mobile SDK be integrated with React Native apps?
We always guarantee support for the current and the previous version of iOS. Trying to support reaching a large portion of the iOS device base while also increasing the quality and efficiency of the SDK by incorporating newer and newer platform features is a delicate balancing act. As iOS devices are typically upgraded to the latest version soon after a new release is available, this in practice means that at least 95% of the iOS user base can always be reached. Currently this means iOS 11 and iOS 12. Having said that we do not automatically deprecate support for iOS 11 when e.g. iOS 13 is released. We will only deprecate support for iOS 11 when implementing some new functionality into the SDK can not any more be effectively done by using iOS 11 platform features. When this happens we issue a notice at least 3 month in advance about the planned change in platform support.
We only offer support for the latest version of the SDK. If you run an earlier version of the SDK and report a bug, we will fix the bug only if it is still reproducible with the latest SDK version and ask you to upgrade to the newest version when released with the bug fix. In order to minimise disturbance when upgrading to a new version, we have a comprehensive regression test suite and we do our utmost best to maintain backward compatibility. In the rare case when maintaining backward compatibility is not possible, we will provide clear indication of the functionality impacted and suggestions to mitigate the problem.
As React Native gives good support for building wrappers around platform native SDKs, using our Emarsys Mobile SDK in this way is doable but we can not currently offer help to debug problems specific to using the Emarsys Mobile SDK in React Native applications.
Emarsys SDK features an offline queue. All SDK events including logins, logouts, custom events, enter this queue first. As long as the device is online, this queue is processed and events get sent to the Mobile Engage backend continuously. While the device is offline, the queue stores the SDK events temporarily and when the SDK detects that network connectivity is back, it restarts the event sending. The events stay in the queue until response from the server is received, so the SDK can resend events in case a network error or a timeout occurs during sending or the server responds with a recoverable error code. If the server responds with a non-recoverable error code, e.g. authentication failure, the event is discarded.