AB#280444 - Add GamifyWidget SDK module

[dmytro-b-optimove]

Summary

• Adds GamifyWidgetSDK — public entry point with initialize(widgetUrl:) and open(from:userId:token:) that presents a modal sheet
• Adds GamifyWidgetViewController — internal UIKit view controller hosting a WKWebView with JS bridge (READY → INIT → CLOSE handshake), loading spinner, and error state
• Adds GamifyWidgetSDKTests — unit tests for URL initialisation

iOS equivalent of Android SDK PR #91 (AB#280444). No changes to Package.swift — new files sit inside the existing OptimoveSDK target source path.

JS Bridge

Widget fires READY → native responds with INIT (userId/token) via window.postMessage. Widget calls window.webkit.messageHandlers.nativeBridge.postMessage to close. Token is redacted in logs.

Test plan

• cmd+U on OptimoveSDK scheme — GamifyWidgetSDKTests pass
• cmd+B on iOS scheme — clean build, no errors or warnings
• Run QA app, navigate to Gamify Widget, fill tenant + userId, tap Open Widget — sheet opens and close button dismisses

[Copilot]

Pull request overview

Adds a new “Gamify Widget” feature area to the OptimoveSDK, providing a public SDK entry point to configure a widget URL and present a modal sheet hosting a WKWebView with a simple JS bridge handshake.

Changes:

• Introduces GamifyWidgetSDK as the public API for configuring and opening the widget.
• Adds GamifyWidgetViewController to host the WKWebView, show loading/error UI, and handle READY/INIT/CLOSE messages.
• Adds GamifyWidgetSDKTests covering URL initialization behavior (including a background-thread call case).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
OptimoveSDK/Sources/Classes/GamifyWidget/GamifyWidgetSDK.swift	Public entry point to initialize widget URL and present the widget as a modal sheet.
OptimoveSDK/Sources/Classes/GamifyWidget/GamifyWidgetViewController.swift	Internal UIKit controller with WKWebView + JS bridge, loading spinner, and error state.
OptimoveSDK/Tests/Sources/GamifyWidget/GamifyWidgetSDKTests.swift	Unit tests validating widget URL initialization behavior.

Comments suppressed due to low confidence (1)

OptimoveSDK/Tests/Sources/GamifyWidget/GamifyWidgetSDKTests.swift:21

• Same issue as above: this test asserts immediately after calling initialize, but initialize may be async if invoked off the main thread. Make the test deterministic by running the call on the main thread or waiting until the main-queue work has executed.

    func testInitializeOverwritesPreviousUrl() {
        GamifyWidgetSDK.initialize(widgetUrl: "https://first.example.com")
        GamifyWidgetSDK.initialize(widgetUrl: "https://second.example.com")
        XCTAssertEqual(GamifyWidgetSDK.widgetUrl, "https://second.example.com")
    }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dmytro-b-optimove]

Logger is already usable without an explicit import OptimoveCore
https://github.com/optimove-tech/Optimove-SDK-iOS/blob/feature/280444-gamify-widget-ios/OptimoveSDK/Sources/Classes/OptimoveConfig.swift

[eligutovsky]

Hmm, interesting how it was linked then

[dmytro-b-optimove]

Empty/invalid widgetUrl doesn't produce a blank sheet — GamifyWidgetViewController.loadWidget() guards via URL(string:) and falls through to showError(), which reveals the error label set up in setupErrorLabel() (L80-L102):

"Unable to load widget.\nCheck your connection and try again."

[eligutovsky]

How does this error message help a user?
Copilot says not to open the error screen if we know that the user will see it immediately.