> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/documentation/sdk/domains-api/environment/isminversionsupported.md).

# isMinVersionSupported

> 함수형 API `isMinVersionSupported`로도 같은 기능을 쓸 수 있어요.

### 기능 설명 <a href="#description" id="description"></a>

현재 토스 앱 버전이 플랫폼별 최소 지원 버전 이상인지 확인해요. 현재 플랫폼(Android/iOS)에 해당하는 버전 기준으로 비교해요.

* `'always'`를 지정하면 해당 플랫폼에서 항상 `true`를 반환해요.
* `'never'`를 지정하면 해당 플랫폼에서 항상 `false`를 반환해요.
* 샌드박스 환경에서는 버전과 무관하게 항상 `true`를 반환해요.

### 타입 <a href="#type" id="type"></a>

```ts
isMinVersionSupported(minVersions): boolean;
```

**Params**

```ts
{
  android: `${number}.${number}.${number}` | "always" | "never";
  ios: `${number}.${number}.${number}` | "always" | "never";
}
```

**Response**

`boolean`이에요.

### 예시 코드 <a href="#example-code" id="example-code"></a>

```js
import { Environment } from "@apps-in-toss/web-framework";

const supported = Environment.isMinVersionSupported({
  android: "5.250.0",
  ios: "always",
});

if (!supported) {
  console.warn("현재 토스앱 버전에서는 이 기능을 사용할 수 없어요.");
}
```


---

# 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://developers-apps-in-toss.toss.im/documentation/sdk/domains-api/environment/isminversionsupported.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.