# Debugging & installationId

## 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.

```swift
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:

```swift
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](/sdk/attribution-and-analytics/building-funnels-with-event-tracking.md#validation-rules).
* **Local testing** — confirmation that a `.storekit` file was loaded, or an error if it couldn't be parsed. See [Local Testing](/sdk/advanced-and-tooling/local-testing.md).

## 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:

```swift
Onside.initialize(disableSSLPinning: true)
```

{% hint style="danger" %}
`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.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onside.io/sdk/advanced-and-tooling/debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.