> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.onesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vue JS Web SDK 설정

> onesignal-vue 또는 @onesignal/onesignal-vue3 플러그인을 사용하여 OneSignal 웹 푸시 알림을 Vue.js 애플리케이션에 통합하세요. 원활한 푸시 전달을 위해 Service Worker를 설치, 구성 및 사용자 지정하는 방법을 알아보세요.

export const SdkReleasesIframe = ({sdkFilter = undefined, viewMode = undefined, height, ...frameProps}) => {
  const baseUrl = 'https://onesignal.github.io/sdk-releases';
  const buildUrl = (theme, sdkFilter, viewMode) => {
    const url = new URL(baseUrl);
    const params = new URLSearchParams();
    if (theme) {
      params.set('theme', theme);
    }
    if (sdkFilter) {
      params.set('sdk', sdkFilter);
    }
    if (viewMode) {
      params.set('viewMode', viewMode);
    }
    if (params.toString()) {
      url.search = params.toString();
    }
    return url.toString();
  };
  const detectTheme = () => {
    if (document.documentElement.classList.contains('dark')) {
      return 'dark';
    }
    return 'light';
  };
  const [theme, setTheme] = useState('light');
  const [iframeSrc, setIframeSrc] = useState(() => {
    const initialTheme = detectTheme();
    return buildUrl(initialTheme, sdkFilter, viewMode);
  });
  useEffect(() => {
    const currentTheme = detectTheme();
    setTheme(currentTheme);
    setIframeSrc(buildUrl(currentTheme, sdkFilter, viewMode));
    const mediaQuery = window.matchMedia('(prefers-color-scheme: dark)');
    const handleThemeChange = () => {
      const newTheme = detectTheme();
      setTheme(newTheme);
      setIframeSrc(buildUrl(newTheme, sdkFilter, viewMode));
    };
    if (mediaQuery.addEventListener) {
      mediaQuery.addEventListener('change', handleThemeChange);
    } else {
      mediaQuery.addListener(handleThemeChange);
    }
    window.addEventListener('storage', handleThemeChange);
    const observer = new MutationObserver(handleThemeChange);
    observer.observe(document.documentElement, {
      attributes: true,
      attributeFilter: ['class', 'data-theme']
    });
    return () => {
      if (mediaQuery.removeEventListener) {
        mediaQuery.removeEventListener('change', handleThemeChange);
      } else {
        mediaQuery.removeListener(handleThemeChange);
      }
      window.removeEventListener('storage', handleThemeChange);
      observer.disconnect();
    };
  }, [sdkFilter, viewMode]);
  const getIframeHeight = () => {
    if (viewMode === 'table') {
      return '450';
    }
    if (viewMode === 'mini') {
      return '170';
    }
    return '800';
  };
  const iframeHeight = height || getIframeHeight();
  return <Frame {...frameProps}>
      <iframe src={iframeSrc} width="100%" height={iframeHeight} frameBorder="0" style={{
    border: "none"
  }} title="SDK Releases" key={iframeSrc} />
    </Frame>;
};

<SdkReleasesIframe sdkFilter="vue" viewMode="mini" />

## 개요

이 가이드에서는 OneSignal 푸시 알림을 Vue.js 애플리케이션에 통합하는 방법을 설명합니다. Service Worker 구성 및 TypeScript 지원을 포함한 주요 설정 고려 사항과 함께 공식 OneSignal Vue 플러그인을 사용하여 Vue 2 및 Vue 3를 모두 다룹니다.

***

## 요구 사항

* 구성된 OneSignal 앱 및 플랫폼. 시작하려면 [웹 푸시 설정](./web-push-setup)을 참조하세요.

### Vue 호환성

Vue 환경과 호환되는 플러그인 버전을 설치했는지 확인하세요.

| Vue | OneSignal Plugin                                              |
| --- | ------------------------------------------------------------- |
| 2   | [onesignal-vue](https://github.com/OneSignal/onesignal-vue)   |
| 3   | [onesignal-vue3](https://github.com/OneSignal/onesignal-vue3) |

***

## 설치

선호하는 패키지 관리자를 통해 설치하세요:

<CodeGroup>
  ```bash yarn theme={null}
  yarn add onesignal-vue
  # or yarn add @onesignal/onesignal-vue3
  ```

  ```bash npm theme={null}
  npm install --save onesignal-vue
  # or npm install --save @onesignal/onesignal-vue3
  ```
</CodeGroup>

***

## 초기화

OneSignal 서비스를 가져와서 루트 컴포넌트에서 초기화하세요. `init` 함수는 OneSignal이 로드될 때 해결되는 프로미스를 반환합니다.

[키 및 ID](./keys-and-ids)에서 찾을 수 있는 OneSignal 앱 ID로 `YOUR_APP_ID`를 바꾸세요.

<CodeGroup>
  ```javascript Vue2 theme={null}
  import Vue from 'vue'
  import OneSignalVue from 'onesignal-vue'

  Vue.use(OneSignalVue);

  new Vue({
    render: h => h(App),
    beforeMount() {
      this.$OneSignal.init({ appId: 'YOUR_APP_ID' });
    }
  }).$mount('#app')
  //Example 1
  await this.$OneSignal.init({ appId: 'YOUR_APP_ID' });
  // do other stuff

  //Example 2
  this.$OneSignal.init({ appId: 'YOUR_APP_ID' }).then(() => {
    // do other stuff
  });
  ```

  ```javascript Vue3 theme={null}
  /*
  Vue 3에서는 OneSignal 초기화 옵션을 `use` 함수의 인수로 직접 전달할 수 있습니다. 코드 완성과 같은 편집기의 이점을 선호하는 경우 별도로 초기화할 수도 있습니다.
  */
  import { createApp } from 'vue'
  import OneSignalVuePlugin from '@onesignal/onesignal-vue3'

  createApp(App).use(OneSignalVuePlugin, {
    appId: 'YOUR_APP_ID',
  }).mount('#app');

  // OR

  import { createApp } from 'vue'
  import OneSignalVuePlugin from '@onesignal/onesignal-vue3'

  createApp(App).use(OneSignalVuePlugin).mount('#app');

  // component
  this.$OneSignal.init({
    appId: "YOUR_APP_ID"
  });
  ```
</CodeGroup>

OneSignal 플러그인은 애플리케이션 내부에서 액세스할 수 있는 `$OneSignal` 전역 속성을 자동으로 노출합니다.

### Composition API

[`setup`](https://vuejs.org/api/composition-api-setup.html#basic-usage) 내에서 호출할 수 있는 `useOneSignal()` 훅을 통해 Vue의 [Composition API](https://vuejs.org/guide/extras/composition-api-faq.html)를 활용할 수도 있습니다.

### init 옵션 사용자 지정

추가 [`init` 매개변수](./web-sdk-reference#init)로 초기화를 사용자 지정할 수 있습니다.

### Service Worker 설정

아직 수행하지 않았다면 사이트에 추가할 [OneSignal Service Worker 파일을 다운로드](https://github.com/OneSignal/OneSignal-Website-SDK/files/11480764/OneSignalSDK-v16-ServiceWorker.zip)해야 합니다.

`OneSignalSDKWorker.js` 파일은 공개적으로 액세스할 수 있어야 합니다. `public` 디렉토리, 최상위 루트 또는 하위 디렉토리에 넣을 수 있습니다. 그러나 파일을 하위 디렉토리에 배치하거나 사이트에 다른 Service Worker가 있는 경우 경로를 지정해야 합니다. 자세한 내용은 [OneSignal Service Worker](./onesignal-service-worker)를 참조하세요.

| 옵션                   | 설명                                                                                                     |
| -------------------- | ------------------------------------------------------------------------------------------------------ |
| `serviceWorkerParam` | OneSignal worker가 제어하는 범위입니다. **권장 사항:** 사용자 지정 하위 경로를 사용하세요(예: `"/onesignal/"`).                      |
| `serviceWorkerPath`  | 호스팅된 OneSignal Service Worker 파일의 경로입니다(예: `"onesignal/OneSignalSDKWorker.js"`). 공개적으로 액세스할 수 있어야 합니다. |

**예시:**

```javascript theme={null}
this.$OneSignal.init({
  appId: 'YOUR-ONESIGNAL-APP-ID',
  serviceWorkerParam: {
    scope: '/onesignal/'
  },
  serviceWorkerPath: 'onesignal/OneSignalSDKWorker.js'
});
```

#### Worker 호스팅

* 공개 루트(기본값): `/OneSignalSDKWorker.js`
* 사용자 지정 폴더(권장): 예: 이전 단계에서 설정한 대로 `/onesignal/OneSignalSDKWorker.js`.

#### Service Worker 호스팅 확인

브라우저에서 경로를 방문하여 액세스할 수 있는지 확인하세요.

루트를 사용한 경우:

```
https://your-site.com/OneSignalSDKWorker.js
```

예시 경로를 사용하는 경우:

```
https://your-site.com/onesignal/OneSignalSDKWorker.js
```

유효한 JavaScript를 반환해야 합니다.

### 중요 사항

* 개발 환경에서 중복 초기화 방지
  * 개발 환경에서 테스트할 때 OneSignal SDK가 두 번 초기화되어 콘솔 오류가 발생할 수 있습니다.
  * 이는 `<React.StrictMode>`가 개발 환경에서 효과를 두 번 실행하기 때문에 발생합니다. 이를 해결하려면 개발 중에 루트 컴포넌트에서 `<React.StrictMode>`를 제거하세요.

<Warning>
  Strict 모드는 개발 환경에만 영향을 미치며 프로덕션 빌드에는 영향을 미치지 않습니다.
</Warning>

***

## Testing the OneSignal SDK integration

This guide helps you verify that your OneSignal SDK integration is working correctly by testing push notifications and subscription registration.

### Check web push subscriptions

<Steps>
  <Step title="Launch your site on a test device.">
    * Use Chrome, Firefox, Edge, or Safari while testing.
    * **Do not use Incognito or private browsing mode.** Users cannot subscribe to push notifications in these modes.
    * The prompts should appear based on your [permission prompts](/docs/en/permission-requests) configuration.
    * Click **Allow** on the native prompt to subscribe to push notifications.

    <Frame caption="Web push native permission prompt">
      <img src="https://mintcdn.com/onesignal/FXJz6yFfOqztaEND/images/push/web-push-native-permission-prompt.png?fit=max&auto=format&n=FXJz6yFfOqztaEND&q=85&s=91c15dd6677de6a0ba37da20449ccca1" alt="사용자에게 알림 허용 또는 차단을 묻는 브라우저 기본 권한 프롬프트" width="1724" height="974" data-path="images/push/web-push-native-permission-prompt.png" />
    </Frame>
  </Step>

  <Step title="Check your OneSignal dashboard">
    * Go to **Audience > Subscriptions**.
    * You should see a new entry with the status **Subscribed**.

    <Frame caption="Dashboard showing subscription with 'Subscribed' status">
      <img src="https://mintcdn.com/onesignal/KPVdijCt4_xCbkO8/images/dashboard/web-push-subscription-status.png?fit=max&auto=format&n=KPVdijCt4_xCbkO8&q=85&s=786e9c5e4131f01fef20d11bebd1a3d0" alt="OneSignal 대시보드 구독 페이지에 Subscribed 상태의 웹 푸시 구독이 표시됨" width="1188" height="742" data-path="images/dashboard/web-push-subscription-status.png" />
    </Frame>

    <Check>You have successfully created a [web push subscription](/docs/en/subscriptions).
    Web push subscriptions are created when users first subscribe to push notifications on your site.</Check>
  </Step>
</Steps>

### Set up test users

test users are helpful for testing a push notification before sending a message.

<Steps>
  <Step title="Add to Test Users.">
    In the dashboard, next to the subscription, click the **Options (three dots)** button and select **Add to Test Users**.

    <Frame caption="Adding a device to Test Users">
      <img src="https://mintcdn.com/onesignal/NCUI56Tiw7V-s0dT/images/dashboard/add-to-test-subscriptions.png?fit=max&auto=format&n=NCUI56Tiw7V-s0dT&q=85&s=2455d4cd74ea4ad686f76730cd95bbaa" alt="구독의 옵션 메뉴에 테스트 구독에 추가 옵션이 표시됨" width="1188" height="742" data-path="images/dashboard/add-to-test-subscriptions.png" />
    </Frame>
  </Step>

  <Step title="Name your subscription.">
    Name the subscription so you can easily identify your device later in the **test users tab**.
  </Step>

  <Step title="Create a test users segment.">
    Go to **Audience > Segments > New Segment**.
  </Step>

  <Step title="Name the segment.">
    Name the segment `Test Users` (the name is important because it will be used later).
  </Step>

  <Step title="Add the Test Users filter and click Create Segment.">
    <Frame caption="Creating a 'Test Users' segment with the Test Users filter">
      <img src="https://mintcdn.com/onesignal/NCUI56Tiw7V-s0dT/images/dashboard/create-test-users-segment.png?fit=max&auto=format&n=NCUI56Tiw7V-s0dT&q=85&s=91b8a021be6e83662854e68ec3e1da04" alt="Test Users 필터가 선택되고 세그먼트 이름이 Test Users인 세그먼트 편집기" width="1188" height="742" data-path="images/dashboard/create-test-users-segment.png" />
    </Frame>

    <Check>You have successfully created a segment of test users.
    We can now test sending messages to this individual device and groups of test users.</Check>
  </Step>
</Steps>

### Send test push via API

<Steps>
  <Step title="Get your App API Key and App ID.">
    In your OneSignal dashboard, go to **Settings > [Keys & IDs](/docs/en/keys-and-ids)**.
  </Step>

  <Step title="Update the provided code.">
    Replace `YOUR_APP_API_KEY` and `YOUR_APP_ID` in the code below with your actual keys. This code uses the `Test Users` segment we created earlier.

    ```curl theme={null}
    curl -X \
    POST --url 'https://api.onesignal.com/notifications' \
     --header 'content-type: application/json; charset=utf-8' \
     --header 'authorization: Key YOUR_APP_API_KEY' \
     --data \
     '{
      "app_id": "YOUR_APP_ID",
      "target_channel": "push",
      "name": "Testing basic setup",
      "headings": {
      	"en": "👋"
      },
      "contents": {
        "en": "Hello world!"
      },
      "included_segments": [
        "Test Users"
      ],
      "chrome_web_image": "https://avatars.githubusercontent.com/u/11823027?s=200&v=4"
    }'
    ```
  </Step>

  <Step title="Run the code.">
    Run the code in your terminal.
  </Step>

  <Step title="Check images and confirmed receipt.">
    If all setup steps were completed successfully, the test users should receive a notification.

    <Warning>Only Chrome supports images. Images will appear small in the collapsed notification view. Expand the notification to see the full image.</Warning>

    <Frame caption="Expanded push notification with image on Chrome macOS">
      <img src="https://mintcdn.com/onesignal/FXJz6yFfOqztaEND/images/push/web-push-image.png?fit=max&auto=format&n=FXJz6yFfOqztaEND&q=85&s=8dd90279daff9e24d3fd281e73aa1e74" alt="macOS Chrome에서 커스텀 이미지가 표시된 확장된 푸시 알림" width="740" height="896" data-path="images/push/web-push-image.png" />
    </Frame>
  </Step>

  <Step title="Check for confirmed receipt.">
    In your dashboard, go to **Delivery > Sent Messages**, then click the message to view stats. You should see the **confirmed** stat, meaning the device received the push.

    <Note>Safari does not support confirmed receipt.</Note>

    <Card title="푸시 알림 메시지 보고서" icon="chart-bar" href="/docs/en/push-notification-message-reports">
      푸시 알림의 전달, 클릭 및 전환 통계를 확인하세요.
    </Card>
  </Step>
</Steps>

<Check>You have successfully sent a notification via the API to a segment.</Check>

If notifications are not arriving, contact `support@onesignal.com` with the following:

* The API request and response (copy-paste into a `.txt` file)
* Your Subscription ID
* Your website URL with the OneSignal code

***

## User identification

The previous section covered creating web push [Subscriptions](/docs/en/subscriptions). This section expands to identifying [Users](/docs/en/users) across all their subscriptions (including push, email, and SMS) using the OneSignal SDK. It covers External IDs, tags, multi-channel subscriptions, privacy, and event tracking to help you unify and engage users across platforms.

### Assign External ID

Use an External ID to identify users consistently across devices, email addresses, and phone numbers using your backend's user identifier. This ensures your messaging stays unified across channels and 3rd party systems (especially important for [Integrations](/docs/en/integrations)).

Set the External ID with the SDK's [`login` method](/docs/en/web-sdk-reference#login-external-id) each time a user is identified by your app.

<Note>
  OneSignal generates unique read-only IDs for subscriptions (Subscription ID) and users (OneSignal ID).

  As users download your app on different devices, subscribe to your website, and/or provide you email addresses and phone numbers outside of your app, new subscriptions will be created.

  Setting the External ID via the SDK is highly recommended to identify users across all their subscriptions, regardless of how they are created.
</Note>

### Add Tags

[Tags](/docs/en/add-user-data-tags) are key-value pairs of string data you can use to store user properties (like `username`, `role`, or preferences) and events (like `purchase_date`, `game_level`, or user interactions). Tags power advanced [Message Personalization](/docs/en/message-personalization) and [Segmentation](/docs/en/segmentation) allowing for more advanced use cases.

Set tags with the SDK's [`addTag` and `addTags` methods](/docs/en/web-sdk-reference#addtag-%2C-addtags) as events occur in your app.

In this example, the user reached level 6 identifiable by the tag called `current_level` set to a value of `6`.

<Frame caption="A user profile in OneSignal with a tag called &#x22;current_level&#x22; set to &#x22;6&#x22;">
  <img src="https://mintcdn.com/onesignal/4HyuQPBpu-4xjmQC/images/docs/d4674261847231079fecc176ba88065409c90943e3854b9df200457325a0aed4-Screenshot_2025-03-18_at_14.47.25.png?fit=max&auto=format&n=4HyuQPBpu-4xjmQC&q=85&s=91083bf83a4c03ea40d485b23f072259" width="1380" height="941" data-path="images/docs/d4674261847231079fecc176ba88065409c90943e3854b9df200457325a0aed4-Screenshot_2025-03-18_at_14.47.25.png" />
</Frame>

We can create a segment of users that have a level of between 5 and 10, and use that to send targeted and personalized messages:

<Frame caption="Segment editor showing a segment targeting users with a current_level value of greater than 4 and less than 10">
  <img src="https://mintcdn.com/onesignal/3zq1PvSaqvUE2bIx/images/docs/300d36b632a6f6d7017780457bbe2610b71767fd0db093c7611e59714dcbda5b-Screenshot_2025-03-18_at_14.49.56.png?fit=max&auto=format&n=3zq1PvSaqvUE2bIx&q=85&s=b84ab0d2c6eedbd6d4e7a2bf15afe103" width="1380" height="941" data-path="images/docs/300d36b632a6f6d7017780457bbe2610b71767fd0db093c7611e59714dcbda5b-Screenshot_2025-03-18_at_14.49.56.png" />
</Frame>

<br />

<Frame caption="Screenshot showing a push notification targeting the Level 5-10 segment with a personalized message">
  <img src="https://mintcdn.com/onesignal/tc0EvmtSSX56SX0c/images/docs/97e09b42d25c6d3f4c7cb0a6fff4dfb8893cbb4b283f7ff1f77977c33113319c-Screenshot_2025-03-18_at_14.55.47.png?fit=max&auto=format&n=tc0EvmtSSX56SX0c&q=85&s=c7839b12057d65a12a4eaddce6e2c11f" width="2764" height="2286" data-path="images/docs/97e09b42d25c6d3f4c7cb0a6fff4dfb8893cbb4b283f7ff1f77977c33113319c-Screenshot_2025-03-18_at_14.55.47.png" />
</Frame>

### Add email and/or SMS subscriptions

The OneSignal SDK creates web push subscriptions automatically when users opt in. You can also reach users through email and SMS channels by creating the corresponding subscriptions.

* Use the [`addEmail` method](/docs/en/web-sdk-reference#addemail-%2C-removeemail) to create email subscriptions.
* Use the [`addSms` method](/docs/en/web-sdk-reference#addsms-%2C-removesms) to create SMS subscriptions.

If the email address and/or phone number already exist in the OneSignal app, the SDK will add it to the existing user, it will not create duplicates.

You can view unified users via **Audience > Users** in the dashboard or with the [View user API](/reference/view-user).

<Frame caption="A user profile with push, email, and SMS subscriptions unified by External ID">
  <img src="https://mintcdn.com/onesignal/56ctKxZSV4m5VEkn/images/docs/b1cf9999d41da6e4ce333e1126612529b85eac47447bb0b434418d082f595acd-Screenshot_2025-03-18_at_14.43.46.png?fit=max&auto=format&n=56ctKxZSV4m5VEkn&q=85&s=7c3885b66e44e097fa0ed7c47f27c911" width="1506" height="848" data-path="images/docs/b1cf9999d41da6e4ce333e1126612529b85eac47447bb0b434418d082f595acd-Screenshot_2025-03-18_at_14.43.46.png" />
</Frame>

<Note>
  Best practices for multi-channel communication

  * Obtain explicit consent before adding email or SMS subscriptions.
  * Explain the benefits of each communication channel to users.
  * Provide channel preferences so users can select which channels they prefer.
</Note>

***

### Privacy & user consent

To control when OneSignal collects user data, use the SDK's consent gating methods:

* [`setConsentRequired(true)`](/docs/en/web-sdk-reference#setconsentrequired): Prevents data collection until consent is given.
* [`setConsentGiven(true)`](/docs/en/web-sdk-reference#setconsentgiven): Enables data collection once consent is granted.

For more on privacy and security:

<Columns cols={2}>
  <Card title="SDK가 수집하는 데이터" icon="database" href="/docs/en/data-collected-by-the-onesignal-sdk">
    OneSignal SDK가 사용자로부터 수집하는 데이터를 확인하세요.
  </Card>

  <Card title="개인 데이터 처리" icon="shield-halved" href="/docs/en/handling-personal-data">
    개인정보 보호 규정에 따라 사용자 데이터를 관리하고 보호하세요.
  </Card>
</Columns>

***

## Listen to push, user, and in-app events

Use SDK listeners to react to user actions and state changes.

The SDK provides several event listeners for you to hook into. See our [SDK reference guide](/docs/en/web-sdk-reference) for more details.

### Push notification events

* [Click event listener](/docs/en/web-sdk-reference#click): Detect when a notification is tapped.
* [Foreground lifecycle listener](/docs/en/web-sdk-reference#foregroundwilldisplay): Control how notifications behave in foreground.

### User state changes

* [User state change event listener](/docs/en/web-sdk-reference#addeventlistener-user-state): Detect when the External ID is set.
* [Permission observer](/docs/en/web-sdk-reference#permissionchange): Track the user's specific interaction with the native push permission prompt.
* [Push subscription change observer](/docs/en/web-sdk-reference#addeventlistener-push-subscription-changes): Track when the push subscription status changes.

***

## Advanced setup & capabilities

Explore more capabilities to enhance your integration:

<Columns cols={3}>
  <Card title="OneSignal로 마이그레이션" icon="rotate" href="/docs/en/migrating-to-onesignal">
    다른 푸시 공급자에서 OneSignal로 이전하세요.
  </Card>

  <Card title="통합" icon="plug" href="/docs/en/integrations">
    OneSignal을 서드파티 도구 및 플랫폼과 연결하세요.
  </Card>

  <Card title="액션 버튼" icon="bell" href="/docs/en/action-buttons">
    푸시 알림에 인터랙티브 버튼을 추가하세요.
  </Card>

  <Card title="다국어 메시징" icon="globe" href="/docs/en/multi-language-messaging">
    사용자의 선호 언어로 현지화된 메시지를 전송하세요.
  </Card>

  <Card title="Identity Verification" icon="shield-check" href="/docs/en/identity-verification">
    서버 측 Identity Verification으로 SDK 통합을 보호하세요.
  </Card>

  <Card title="커스텀 아웃컴" icon="chart-line" href="/docs/en/custom-outcomes">
    메시지와 연결된 커스텀 전환 이벤트를 추적하세요.
  </Card>
</Columns>

### Web SDK setup & reference

<Columns cols={2}>
  <Card title="웹 푸시 설정" icon="gear" href="/docs/en/web-push-setup">
    통합을 위한 모든 핵심 웹 푸시 기능을 활성화하세요.
  </Card>

  <Card title="Web SDK 레퍼런스" icon="code" href="/docs/en/web-sdk-reference">
    사용 가능한 메서드와 구성 옵션에 대한 전체 세부 정보.
  </Card>
</Columns>

<Check>Congratulations! You've successfully completed the Web SDK setup guide.</Check>

***

<Info>
  도움이 필요하신가요?

  지원 팀과 채팅하거나 `support@onesignal.com`으로 이메일을 보내주세요.

  다음을 포함해 주세요:

  * 발생한 문제의 세부 정보 및 재현 단계(가능한 경우)
  * OneSignal 앱 ID
  * External ID 또는 Subscription ID(해당하는 경우)
  * OneSignal 대시보드에서 테스트한 메시지의 URL(해당하는 경우)
  * 관련 [로그 또는 오류 메시지](/docs/ko/capturing-a-debug-log)

  기꺼이 도와드리겠습니다!
</Info>