🤔Frequently Asked Questions

🔆 Forcing Light/Dark UI

By default the iAdvize Mobile SDK displays its UI following the user settings choice on light/dark mode. It is however possible to force the light/dark mode to a given value.

Android

Using setDefaultNightMode inside the Application object will force the app, and thus the SDK Chatbox, to be displayed in the chosen mode:

class App : Application() {
  override fun onCreate() {
    super.onCreate()
    AppCompatDelegate.setDefaultNightMode(MODE_NIGHT_NO)
  }
}

iOS

📣 Updating targeting language

The iAdvize Mobile SDK has a navigation process that is language dependent. That means that when the targeting language is updated inside the client application (for instance in apps offering multiple languages support) the targeting process must be updated in order for the engagement process to be functional again. This can be easily done by calling activateTargetingRule right after updating the targeting language:

Android

IAdvizeSDK.targetingController.language = LanguageOption.Custom(Language.fr)
IAdvizeSDK.targetingController.activateTargetingRule(rule)

iOS

React Native

Flutter

This only concerns the targeting language. For information about the SDK localization, check 🌍 Interface localization.

🌍 Interface localization

The iAdvize Mobile SDK supports the localization of its interface in 14 languages:

• Czech

• Danish

• Dutch

• English

• French

• German

• Italian

• Lithuanian

• Portuguese

• Spanish

• Polish

• Romanian

• Slovak

• Swedish

The localization is automatic but you may need to check that your project meets the requirements, depending on the platform.

Android

The localization is automatic, there are no further steps required.

iOS

If your app runs in a language that does not belong to the supported languages, the iAdvize Mobile SDK will be localized in English.

This only concerns the interface language. For information about the targeting language, check 📣 Updating targeting language.

🚦 Testing the SDK on Android

If you are running unit tests that implies the SDK, some additional steps may be needed.

The Android SDK uses two device system constants that are not instantiated inside the unit test flow, you will have to register them inside your unit tests initiation:

ReflectionHelpers.setStaticField(android.os.Build::class.java, "MODEL", "whatever")
ReflectionHelpers.setStaticField(android.os.Build::class.java, "MANUFACTURER", "whatever")

Please also be sure to initialize the SDK during the unit tests setup (see the Setting up the SDK section).

🔀 Threading on iOS

The iAdvize iOS SDK offers several callbacks through delegate methods and completion handlers.

In most cases, these callbacks are used to perform UI-related tasks. To ensure thread safety, the majority of the SDK's delegates and completion handlers are annotated with the @MainActor keyword. This guarantees that the callbacks are always executed on the main thread.

An important exception is the JWEProvider protocol and its willRequestJWE(completion:) method. Neither the protocol nor the method's completion handler are annotated with @MainActor. This design choice allows your JWEProvider implementation to operate independently of the main thread. You are free to invoke the completion handler from any thread, based on your implementation's requirements.

More broadly, the iAdvize iOS SDK is fully compatible with apps using Swift Concurrency and Swift 6 Language Mode. It is important not to use @preconcurrency when importing the iAdvize iOS SDK, as it is designed to integrate seamlessly without additional annotations.