> For the complete documentation index, see [llms.txt](https://onestore-dev.gitbook.io/dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onestore-dev.gitbook.io/dev/eng/tools/alc/upgrading-from-v1-to-v2.md).

# Upgrading from V1 to V2

### Upgrading from V1 to V2 <a href="#upgradingfromv1tov2-upgradingfromv1tov2" id="upgradingfromv1tov2-upgradingfromv1tov2"></a>

#### 1. Add ALC library dependencies <a href="#upgradingfromv1tov2-1.addalclibrarydependencies" id="upgradingfromv1tov2-1.addalclibrarydependencies"></a>

Starting from ONE store SDK ALC v2, distribution is provided through maven.

To apply the SDK through maven, the following must be applied.

<br>

**Delete ALC AAR file**

Delete the alc-android-library\_v1.0.0.aar file in the libs folder of the Project

**Add maven dependencies**

Register the ONE store maven address in the project top-level build.gradle file.

{% hint style="warning" %}
For the Android Studio (version: bumblebee), add from settings.gradle.
{% endhint %}

```gradle

...
buildscript {
repositories {
...
    maven { url 'https://repo.onestore.net/repository/onestore-sdk-public' }
}
}
...

```

Add the ONE store ALC library dependency to the build.gradle file of the following app.

```gradle

...
dependencies {
def onestore_sdk_version = "2.0.0"
implementation "com.onestorecorp.sdk:sdk-licensing:$onestore_sdk_version"
}
...
```

<br>

**Add queries to AndroidManifest.xml**

Please refer to the ONE store notices for setting up the following two cases:

* [For Target SDK version set to 30 (OS11) or higher](https://dev.onestore.co.kr/devpoc/support/news/noticeView.omp?pageNo=4\&noticeId=32968\&viewPageNo=\&searchValue=)
* [For Target SDK version set to 31 (OS12) or higher](https://dev.onestore.co.kr/devpoc/support/news/noticeView.omp?pageNo=1\&noticeId=33072\&viewPageNo=\&searchValue=)

<br>

For Android 11 (Target SDK 30) or higher, the following must be added.

{% hint style="warning" %}
For Android 11 or higher (Target SDK 30 or higher), you must add queries.
{% endhint %}

```xml

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.dev.sample">    
<queries>        
<intent>
            <action android:name="com.onestore.extern.licensing.LicensingService.ACTION" />
        </intent>
        <intent>
            <action android:name="android.intent.action.VIEW" />
            <data android:scheme="onestore" />
        </intent>
    </queries>
...
```

<br>

#### 2. Add SDK Configuration <a href="#upgradingfromv1tov2-2.addsdkconfiguration" id="upgradingfromv1tov2-2.addsdkconfiguration"></a>

ALC v2 requires the sdk-configuration library to apply the required param for use in the SDK.&#x20;

To apply this, add the ONE store sdk-configuration library dependency to the build.gradle file.

```gradle

...
dependencies {
def onestore_configuration_version = "1.0.0"
implementation "com.onestorecorp.sdk:sdk-configuration-kr:$onestore_configuration_version"
}
...
```

<br>

<br>


---

# 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 dynamically by asking a question.

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

```
GET https://onestore-dev.gitbook.io/dev/eng/tools/alc/upgrading-from-v1-to-v2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
