Debugging & installationId

Diagnostics for OnsideKit: the installationId publisher, SDK console logging, and the SSL-pinning debug switch.

installationId

Onside.installationId publishes the SDK's server-issued, anonymous install identifier. It's the value to include in support tickets and to correlate a device with server-side records.

static let installationId: AnyPublisher<String?, Never>

It emits nil while the id is loading (or on error) and a non-nil String once resolved. Subscribe with Combine:

import Combine
import OnsideKit

var cancellables = Set<AnyCancellable>()

Onside.installationId
    .compactMap { $0 }
    .sink { id in
        print("Onside installation id: \(id)")
    }
    .store(in: &cancellables)

OnsideKit attaches this id to its requests automatically — you don't need to send it yourself.

Console logging

OnsideKit prints diagnostic messages prefixed with [Onside]:. Watch for them during development:

• Used before initialization — a warning that an API was called before Onside.initialize().

• Event validation — warnings when an event name or parameter is truncated or dropped. See Building funnels with event tracking.

• Local testing — confirmation that a .storekit file was loaded, or an error if it couldn't be parsed. See Local Testing.

Disabling SSL pinning (debug only)

To inspect SDK network traffic through a TLS-intercepting proxy (e.g. Charles or Proxyman), disable certificate pinning at initialization:

Onside.initialize(disableSSLPinning: true)

disableSSLPinning is a debugging aid only. The setting is persisted across launches, and disabling pinning weakens transport security — never ship it enabled. Leave it false (the default) in production builds.