개요
이 가이드는 Huawei AppGallery에 배포되는 Unity 애플리케이션에 OneSignal 푸시 알림을 통합하는 방법을 설명합니다. 앱이 Huawei AppGallery에 배포되는 경우에만 이 지침을 따르세요.요구 사항
- Android Studio
- “Huawei App Gallery”가 설치된 Huawei 기기
- 구성된 OneSignal 앱 및 플랫폼
OneSignal 앱 및 플랫폼 구성
푸시 알림에 필요한 설정 OneSignal로 푸시 알림 전송을 시작하려면 먼저 지원하는 모든 플랫폼(Apple (APNs), Google (FCM), Huawei (HMS) 및/또는 Amazon (ADM))으로 OneSignal 앱을 구성해야 합니다.OneSignal 앱 구성을 위한 단계별 지침.
OneSignal 앱 구성을 위한 단계별 지침.
앱 만들기 또는 선택
- 기존 앱에 플랫폼을 추가하려면 OneSignal 대시보드에서 설정 > 푸시 및 인앱으로 이동합니다.
- 처음부터 시작하려면 New App/Website를 클릭하고 프롬프트를 따릅니다.

새 앱 만들기를 보여주는 예제.
플랫폼 설정 및 활성화
- 앱 및 조직에 대해 명확하고 인식 가능한 이름을 선택합니다.
- 구성하려는 플랫폼(iOS, Android 등)을 선택합니다.
- Next: Configure Your Platform을 클릭합니다.

첫 번째 OneSignal 앱, 조직 및 채널 설정 예제.
플랫폼 자격 증명 구성
- Android: Firebase 자격 증명 설정
- iOS: p8 토큰(권장) 또는 p12 인증서
- Amazon: API 키 생성
- Huawei: OneSignal 권한 부여
대상 SDK 선택

문서로 이동할 사용 중인 SDK 선택.
SDK 설치 및 앱 ID 저장

앱 ID를 저장하고 추가 팀 구성원을 초대합니다.
설정
1. OneSignal SDK 설정
OneSignal Unity SDK 설정
2. Huawei 구성
OneSignal의 Huawei 플랫폼 설정 Huawei 구성 파일 (agconnect-services.json) AppGallery Connect 프로젝트 목록에서 앱을 선택합니다. C”agconnect-services.json” 버튼을 클릭하여 이 파일을 다운로드합니다.

3. 서명 인증서 지문 생성
4. Huawei gradle 플러그인 및 의존성 추가
Unity 2019.3 이상
Unity 2019.3 이상

// GENERATED BY UNITY. REMOVE THIS COMMENT TO PREVENT OVERWRITING WHEN EXPORTING AGAIN을 제거합니다.- dependencies아래에- implementation 'com.huawei.hms:push:6.3.0.304'를 추가합니다.

Unity 2019.2 이하
Unity 2019.2 이하

// GENERATED BY UNITY. REMOVE THIS COMMENT TO PREVENT OVERWRITING WHEN EXPORTING AGAIN을 제거합니다.- buildscript { repositories }아래에- maven { url 'http://developer.huawei.com/repo/' }를 추가합니다.
- buildscript { dependencies }아래에- classpath 'com.huawei.agconnect:agcp:1.6.5.300'을 추가합니다.
- allprojects { repositories }아래에- maven { url 'http://developer.huawei.com/repo/' }를 추가합니다.

allprojects {} 아래에 다음을 추가합니다.dependencies 아래에 implementation 'com.huawei.hms:push:6.3.0.304'를 추가합니다.
apply plugin: 'com.huawei.agconnect'를 추가합니다.추가 구성 단계
Huawei 위치 서비스 구성 (선택 사항)
mainTemplate.gradle의dependencies 아래에 implementation 'com.huawei.hms:location:<HUAWEI HMS VERSION #>를 추가합니다.

Huawei 문제 해결
테스트하는 동안 OneSignal setLogLevel 메서드를 VERBOSE로 설정해야 합니다. 로그를 확인하여 발생하는 오류와 Huawei 일반 오류 코드를 확인하세요.6003 오류
6003 오류
pushToken을 등록할 때 6003 오류를 방지하려면 디버그 또는 릴리스 키스토어 서명을 생성해야 할 수 있습니다(올바른 앱 빌드 경로 debug 또는 release 선택). “서명 구성” 섹션을 참조하세요.notification_types: -28
notification_types: -28
build.gradle에 com.huawei.hms:push만 있으면 이 특정 오류가 더 이상 발생하지 않습니다. 그러나 공격적인 Proguard 또는 R8 설정이 있는 경우 문제가 발생할 수 있습니다. 문제의 근본 원인인지 확인하기 위해 minifyEnabled를 일시적으로 끄는 것이 좋습니다.또한 다른 HMS 라이브러리의 주요 릴리스 버전을 혼합해서는 안 됩니다. 4 또는 5 중 하나로 시작하세요. 3에서 5까지 혼합하지 않도록 주의하세요. 이는 다른 오류를 생성합니다.Huawei 푸시 토큰을 가져오는 오류
Huawei 푸시 토큰을 가져오는 오류
Testing the OneSignal SDK integration
This guide helps you verify that your OneSignal SDK integration is working correctly by testing push notifications, subscription registration, and in-app messaging.- Go to Device Manager in Android Studio.
- Select your emulator device and click Edit.
- Go to Additional Settings or More.
- Set the Boot option to Cold Boot.
- Save changes and restart the emulator.
Check mobile subscriptions
Launch your app on a test device.
requestPermission method during initialization.
iOS and Android push permission prompts
Check your OneSignal dashboard
- Go to Audience > Subscriptions.
- You should see a new entry with the status “Never Subscribed”.

Dashboard showing subscription with 'Never Subscribed' status
Return to the app and tap Allow on the prompt.
Refresh the OneSignal dashboard Subscription's page.

Dashboard showing subscription with 'Subscribed' status
Set up test subscriptions
Test subscriptions are helpful for testing a push notification before sending a message.Add to Test Subscriptions.

Adding a device to Test Subscriptions
Name your subscription.

Dashboard showing the 'Name your subscription' field
Create a test users segment.
Name the segment.
Test Users (the name is important because it will be used later).Add the Test Users filter and click Create Segment.

Creating a 'Test Users' segment with the Test Users filter
Send test push via API
Get your App API Key and App ID.
Update the provided code.
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.Run the code.
Check images and confirmed delivery.

Push notification with image on iOS and Android
Check for confirmed delivery.

Delivery stats showing confirmed delivery

Confirmed delivery at the device level in Audience Activity
- No image received? Your Notification Service Extension might be missing.
- No confirmed delivery? Review the troubleshooting guide here.
- Having issues? Copy-paste the api request and a log from start to finish of app launch into a .txtfile. Then share both withsupport@onesignal.com.
Send an in-app message
In-app messages let you communicate with users while they are using your app.Close or background your app on the device.
Create an in-app message.
- In your OneSignal dashboard, navigate to Messages > In-App > New In-App.
- Find and select the Welcome message.
- Set your Audience as the Test Users segment we used previously.

Targeting the 'Test Users' segment with an in-app message
Customize the message content if desired.

Example customization of in-app Welcome message
Set Trigger to 'On app open'.
Schedule frequency.

In-app message scheduling options
Make message live.
Open the app and see the message.

Welcome in-app message shown on devices
- Start a new session
- You must close or background the app for at least 30 seconds before reopening. This ensures a new session is started.
- For more, see how in-app messages are displayed.
 
- Still in the Test Userssegment?- If you reinstalled or switched devices, re-add the device to Test Subscriptions and confirm it’s part of the Test Users segment.
 
- Having issues?
- Follow Getting a Debug Log while reproducing the steps above. This will generate additional logging that you can share with support@onesignal.comand we will help investigate what’s going on.
 
- Follow Getting a Debug Log while reproducing the steps above. This will generate additional logging that you can share with 
- Gathering Subscriptions, setting Test subscriptions, and creating Segments.
- Sending Push with images and Confirmed Delivery using Segments and our Create message API.
- Sending In-app messages.
User identification
Previously, we demonstrated how to create mobile Subscriptions. Now we’ll expand to identifying Users across all their subscriptions (including push, email, and SMS) using the OneSignal SDK. We’ll cover 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). Set the External ID with our SDK’slogin method each time they are identified by your app.
Add data tags
Tags are key-value pairs of string data you can use to store user properties (likeusername, role, or preferences) and events (like purchase_date, game_level, or user interactions). Tags power advanced Message Personalization and Segmentation allowing for more advanced use cases.
Set tags with our SDK addTag and addTags methods 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.

A user profile in OneSignal with a tag called "current_level" set to "6"

Segment editor showing a segment targeting users with a current_level value of greater than 4 and less than 10

Screenshot showing a push notification targeting the Level 5-10 segment with a personalized message

The push notification is received on an iOS and Android device with the personalized content
Add email and/or SMS subscriptions
Earlier we saw how our SDK creates mobile subscriptions to send push and in-app messages. You can also reach users through emails and SMS channels by creating the corresponding subscriptions.- Use the addEmailmethod to create email subscriptions.
- Use the addSmsmethod to create SMS subscriptions.

A user profile with push, email, and SMS subscriptions unified by External ID
- 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.
Privacy & user consent
To control when OneSignal collects user data, use the SDK’s consent gating methods:- setConsentRequired(true): Prevents data collection until consent is given.
- setConsentGiven(true): Enables data collection once consent is granted.
Prompt for push permissions
Instead of callingrequestPermission() immediately on app open, take a more strategic approach. Use an in-app message to explain the value of push notifications before requesting permission.
For best practices and implementation details, see our Prompt for push permissions guide.
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 for more details.Push notification events
- addClickListener(): Detect when a notification is tapped. Helpful for Deep Linking.
- addForegroundLifecycleListener(): Control how notifications behave in foreground.
User state changes
- addObserver()for user state: Detect when the External ID is set.
- addPermissionObserver(): Track the user’s specific interaction with the native push permission prompt.
- addObserver()for push subscription: Track when the push subscription status changes.
In-app message events
- addClickListener(): Handle in-app click actions. Ideal for deep linking or tracking events.
- addLifecycleListener(): Track full lifecycle of in-app messages (shown, clicked, dismissed, etc.).
Advanced setup & capabilities
Explore more capabilities to enhance your integration:- 🔁 Migrating to OneSignal from another service
- 🌍 Location tracking
- 🔗 Deep Linking
- 🔌 Integrations
- 🧩 Mobile Service Extensions
- 🛎️ Action buttons
- 🌐 Multi-language messaging
- 🛡️ Identity Verification
- 📊 Custom Outcomes
- 📲 Live Activities
Mobile SDK setup & reference
Make sure you’ve enabled all key features by reviewing the Mobile push setup guide. For full details on available methods and configuration options, visit the Mobile SDK reference.support@onesignal.com으로 이메일을 보내주세요.다음을 포함해 주세요:- 발생한 문제의 세부 정보 및 재현 단계(가능한 경우)
- OneSignal 앱 ID
- External ID 또는 Subscription ID(해당하는 경우)
- OneSignal 대시보드에서 테스트한 메시지의 URL(해당하는 경우)
- 관련 로그 또는 오류 메시지