> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/ios/setup-luciq-for-ios/integrate-luciq-on-ios/one-code-apps-for-ios.md).

# One Code Apps For iOS

Integrate Luciq in iOS apps with multiple targets from a single codebase. Configure Luciq for one-code apps and share SDK settings across app targets.

{% hint style="warning" %}

#### **Minimum Required SDK Version**

One code apps is supported starting iOS SDK v15.1.0
{% endhint %}

### Overview

The **One Code Apps** feature enables teams with **shared code base applications** to integrate multiple app variants under a single Luciq app token. This is ideal for organizations that release the same app to different brands, markets, or regions but want to consolidate stability and performance monitoring.

Instead of creating a separate Luciq application for each variant, you integrate all variants using **one Luciq app token** and identify each variant via the **bundle-id using the App variant API**.

### Integrating One Code Apps

{% stepper %}
{% step %}

#### Get Your Luciq App Token

From your Luciq dashboard, go to your application’s settings and copy the **app token** — this will be used for all variants.
{% endstep %}

{% step %}

#### Set the App Variant Name

Call the method before initializing the SDK:

{% tabs %}
{% tab title="Swift" %}
{% code overflow="wrap" %}

```swift
// Should be called before init
Luciq.appVariant = "bundle-id/brand-name"
```

{% endcode %}
{% endtab %}

{% tab title="Objective-C" %}
{% code overflow="wrap" %}

```objectivec
// Should be called before init
Luciq.appVariant = @"bundle-id/brand-name";
```

{% endcode %}
{% endtab %}
{% endtabs %}
{% endstep %}
{% endstepper %}

{% hint style="success" %}

#### **Best Practice**

Use the **same variant name format** across all apps (e.g., bundle ID or a consistent naming convention) to make filtering easier in the dashboard.

We recommend using the unique part of the the bundle-id, assume your bundle-id is: com.example.123245r454523452.MyApp.US, we recommend setting the app variant as ***MyApp US***.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/ios/setup-luciq-for-ios/integrate-luciq-on-ios/one-code-apps-for-ios.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.