Hikotest on iOS

In Xcode choose File → Add Package Dependencies… and enter the repository URL:

https://github.com/halil9393/HikotestIOSSDK.git

Or declare it in your own Package.swift:

dependencies: [
    .package(url: "https://github.com/halil9393/HikotestIOSSDK.git", branch: "main")
],
targets: [
    .target(
        name: "YourApp",
        dependencies: [.product(name: "HikotestSDK", package: "HikotestIOSSDK")]
    )
]

In the panel, open your project and go to Settings → SDK Integration. You'll see two values with copy buttons:

Configure once — for example in your App struct or AppDelegate — then initialize. The SDK downloads (or loads the cached) release.wasm from the panel and starts its update loop.

import HikotestSDK

@main
struct YourApp: App {
    init() {
        Hikotest.shared.configure(HikotestConfig(
            panelBaseUrl: "https://your-panel.hikotest.app", // from Settings → SDK Integration
            projectId: "your-project-id"                     // from Settings → SDK Integration
        ))
    }

    var body: some Scene {
        WindowGroup {
            ContentView()
                .task {
                    try? await Hikotest.shared.initialize()
                }
        }
    }
}

The recommended path is the generated Swift wrapper. Every deploy writes sdk/swift/HikotestFunctions.swiftinto your project's release — parameter names, types and DocC comments included. Copy it into your app for compile-time-safe calls:

// Signatures and docs come from your panel deploy
let price = try HikotestFunctions.applyCampaign(1000, "VIP30")

You can also call dynamically. Values travel through the type-safe HikoValue enum (.int / .float / .string / .boolean), with up to five named parameters per function:

let result = try Hikotest.shared.execute(
    "applyCampaign",
    signature: "(float,string)->float",
    .float(1000), .string("VIP30")
)

Some functions (payments, pricing, authorization) should never change over-the-air. Download a release you trust from the panel (release.wasm + manifest.json), ship them as bundle resources and pass them at configure time:

Hikotest.shared.configure(HikotestConfig(
    panelBaseUrl: "https://your-panel.hikotest.app",
    projectId: "your-project-id",
    localBundle: LocalBundle(wasmBytes: wasmBytes, manifestJson: manifestJson),
    lockedFunctions: ["applyPayment"] // device-side lock list (optional)
))

• A function runs from the embedded local bundle when the live manifest marks it ota:false (locked in the panel) or it is in your lockedFunctions set. Everything else keeps hot-reloading from the live OTA bundle.
• The device wins. The union is one-way: even if the panel unlocks a function remotely, anything in lockedFunctions keeps running from the embedded bundle until you ship an app update.
• A locked function missing from the embedded bundle throws HikotestError.otaLockedMissing — there is no silent OTA fallback.
• Fully offline mode: configure only localBundle (no panel, no repo) — the SDK never touches the network.
• Hikotest.shared.isLocallyPinned(_:) tells you where calls are served from.

• Every deploy (and rollback) from the panel publishes an immutable release with a bumped bundle version (e.g. v1.0.7).
• A background task periodically asks the panel for the latest version; when a new one appears, the bundle is downloaded, cached and hot-loaded — no app restart, no App Store review.
• The last downloaded bundle is cached locally, so the app starts offline with the most recent logic.
• Wrapper code only changes when a function signature changes; internal logic updates arrive without touching your codebase.

• The runtime is pure Swift (WasmKit) — nothing to notarize, no XCFramework binaries, and swift test style unit tests run on macOS without a simulator.
• The SDK mirrors the Android SDK API one-to-one, so cross-platform teams share the same mental model: configure → initialize → execute.
• "Missing export" on string functions means the bundle predates the current string ABI — redeploy the project from the panel.