> ## 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.
# Flutterflow SDK 설정
> iOS 및 Android용 Flutterflow 앱에 OneSignal Flutter SDK를 추가하는 방법
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
;
};
이 가이드는 Flutterflow 모바일 앱 설정을 위한 것입니다. Flutterflow 사이트가 있는 경우 [웹 SDK 설정](./web-sdk-setup) 가이드를 참조하세요.
## 요구 사항
* Flutterflow 플랜: Standard 이상
* 구성된 OneSignal 앱 및 플랫폼
**iOS 요구 사항**
* Xcode 14+가 있는 macOS(설정 지침은 Xcode 16.2 사용)
* iOS 12+, iPadOS 12+ 또는 iOS 16.2+를 실행하는 Xcode 시뮬레이터가 있는 기기
* CocoaPods 1.16.2+
**Android 요구 사항**
* Google Play 스토어(서비스)가 설치된 Android 7.0+ 기기 또는 에뮬레이터
### OneSignal 앱 및 플랫폼 구성
지원하는 플랫폼(Apple (APNs), Google (FCM), Huawei (HMS), Amazon (ADM))으로 OneSignal 앱을 구성하세요.
조직에 이미 OneSignal 계정이 있는 경우 조직에 [초대를 요청](/docs/ko/manage-team-members)하세요. 그렇지 않은 경우 [무료 계정에 가입](https://onesignal.com)하여 시작하세요.
**New App/Website**를 클릭하여 새 앱을 만들거나 **설정 > 푸시 및 인앱**에서 기존 앱에 플랫폼을 추가합니다. 구성하려는 플랫폼을 선택하고 **Next: Configure Your Platform**을 클릭합니다.
플랫폼에 대한 자격 증명을 입력합니다:
* **Android**: [Firebase 자격 증명 설정](/docs/ko/android-firebase-credentials)
* **iOS**: [p8 토큰(권장)](/docs/ko/ios-p8-token-based-connection-to-apns) 또는 [p12 인증서](/docs/ko/ios-p12-generate-certificates)
* **Amazon**: [API 키 생성](/docs/ko/generate-an-amazon-api-key)
* **Huawei**: [OneSignal 권한 부여](/docs/ko/authorize-onesignal-to-send-huawei-push)
자격 증명을 입력한 후 **Save & Continue**를 클릭합니다.
**앱 ID**가 최종 화면에 표시됩니다. 복사하고 저장하세요 — SDK를 초기화할 때 필요합니다. SDK 플랫폼을 선택한 다음 설정 가이드를 따릅니다.
***
## 설정
### 1. 새 사용자 지정 작업 만들기
Flutterflow 프로젝트에서 Custom Code로 이동한 다음 +Add 버튼을 클릭하고 Action을 선택합니다.
오른쪽 도구 모음의 Action 설정에서 Add Dependency를 클릭하고 다음 종속성을 입력한 다음 새로 고침을 클릭하여 작업에 추가합니다:
```yaml dependency theme={null}
dependencies:
onesignal_flutter: ^5.1.2
```
Action Code에서 미리 로드된 코드 아래에 다음을 추가한 다음 작업을 저장하고 컴파일합니다.
`YOUR_APP_ID`를 OneSignal 대시보드 \*\*설정 > [키 및 ID](./keys-and-ids)\*\*에서 찾을 수 있는 OneSignal 앱 ID로 교체합니다.
OneSignal 앱에 액세스할 수 없는 경우 [팀 구성원](./manage-team-members)에게 초대를 요청하세요.
```javascript Flutter theme={null}
import 'package:onesignal_flutter/onesignal_flutter.dart';
Future onesignal() async {
//Remove this method to stop OneSignal Debugging
OneSignal.Debug.setLogLevel(OSLogLevel.verbose);
OneSignal.initialize("YOUR_APP_ID");
// The promptForPushNotificationsWithUserResponse function will show the iOS or Android push notification prompt. We recommend removing the following code and instead using an In-App Message to prompt for notification permission
OneSignal.Notifications.requestPermission(true);
}
```
다음으로 왼쪽 도구 모음에서 main.dart 파일을 클릭하고 오른쪽 바의 Initial Actions 옆에 있는 + 아이콘을 클릭한 다음 방금 생성된 `onesignal` 작업을 클릭합니다.
이렇게 하면 앱에 작업이 추가되고 앱이 실행될 때 OneSignal SDK가 초기화됩니다:
### 2. 프로젝트 내보내기
Developer Menu를 열고 APK를 다운로드합니다:
APK가 다운로드되면 APK를 Android 에뮬레이터로 드래그하여 설치하여 앱을 테스트할 수 있습니다. 푸시 기능은 즉시 작동해야 하며 네이티브 프롬프트를 통해 푸시 권한을 제공하는 즉시 기기에 푸시 알림을 보낼 수 있습니다.
Developer Menu를 열고 프로젝트 코드를 다운로드합니다:
### 3. iOS 설정
다운로드한 프로젝트는 iOS에서 실행할 준비가 되지 않았을 가능성이 높습니다. OneSignal 특정 추가 사항을 설정하기 전에 프로젝트가 완전히 빌드되었는지 확인해야 합니다. 이를 위해:
* 터미널 창을 열고 다운로드한 프로젝트의 `ios` 폴더로 cd(디렉터리 변경)합니다.
* 터미널에 `flutter build ios`를 입력하고 Enter 키를 누릅니다. 빌드가 완료될 때까지 기다립니다. 프로젝트 크기에 따라 시간이 걸릴 수 있습니다.
* 여전히 터미널에 `pod install`을 입력하고 Enter 키를 누릅니다. Pod 설치가 완료될 때까지 기다립니다.
프로젝트의 ios 폴더에 있는 `.xcworkspace` 파일을 Xcode에서 엽니다.
**루트 프로젝트 > 기본 앱 대상 > Signing & Capabilities**를 선택합니다.
Push Notifications가 활성화되지 않은 경우 **+ Capability**를 클릭하고 **Push Notifications**를 추가합니다. Team 및 Bundle Identifier에 대한 올바른 세부 정보를 입력했는지 확인하세요.
**+ Capability**를 다시 클릭하고 **Background Modes**를 추가합니다. 그런 다음 **Remote notifications**를 선택합니다.
#### Notification Service Extension 추가
OneSignalNotificationServiceExtension을 사용하면 iOS 애플리케이션이 이미지, 버튼 및 배지가 있는 리치 알림을 받을 수 있습니다. OneSignal의 확인된 전달 분석 기능에도 필요합니다.
Xcode에서 \*\*File > New > Target...\*\*을 선택합니다.
**Notification Service Extension**을 선택한 다음 **Next**를 클릭합니다.
제품 이름을 `OneSignalNotificationServiceExtension`으로 입력하고 **Finish**를 누릅니다.
**Finish**를 선택한 후 표시되는 대화 상자에서 스키마를 활성화하지 마세요.
"Activate scheme" 프롬프트에서 **Cancel**을 누릅니다.
**OneSignalNotificationServiceExtension** 대상과 **General** 설정을 선택합니다.
**Minimum Deployments**를 **기본 애플리케이션 대상과 동일한 값**으로 설정합니다. 이는 iOS 11 이상이어야 합니다.
#### App Groups 추가
App Groups를 사용하면 앱이 활성 상태가 아니더라도 알림이 수신될 때 앱과 OneSignalNotificationServiceExtension이 통신할 수 있습니다. 배지 및 확인된 전달에 필요합니다.
**기본 앱 대상 > Signing & Capabilities > + Capability > App Groups**를 선택합니다.
**App Groups** 내에서 **+** 버튼을 클릭합니다.
App Groups 컨테이너를 `group.YOUR_BUNDLE_IDENTIFIER.onesignal`로 설정합니다. 여기서 `YOUR_BUNDLE_IDENTIFIER`는 기본 애플리케이션 "Bundle Identifier"와 동일합니다.
**OK**를 누르고 OneSignalNotificationServiceExtension 대상에 대해 반복합니다.
**OneSignalNotificationServiceExtension Target > Signing & Capabilities > + Capability > App Groups**를 선택합니다.
**App Groups** 내에서 **+** 버튼을 클릭합니다.
App Groups 컨테이너를 `group.YOUR_BUNDLE_IDENTIFIER.onesignal`로 설정합니다. 여기서 `YOUR_BUNDLE_IDENTIFIER`는 \*\*기본 애플리케이션 "Bundle Identifier"\*\*와 동일합니다.
`OneSignalNotificationServiceExtension`을 **포함하지 마세요**.
이 단계는 기본 앱 그룹 이름(`group.{your_bundle_id}.onesignal`)을 사용하지 **않으려는** 경우에만 필요합니다.
`Info.plist` 파일을 열고 `String` 유형으로 새 `OneSignal_app_groups_key`를 추가합니다.
마지막 단계에서 확인한 그룹 이름을 값으로 입력합니다.
`OneSignalNotificationServiceExtension` 폴더 아래의 `Info.plist`에 대해서도 동일하게 수행해야 합니다.
#### OneSignalNotificationServiceExtension에 OneSignal SDK 추가
`ios/Podfile`을 업데이트하여 다음을 포함합니다:
```ruby Podfile theme={null}
target 'OneSignalNotificationServiceExtension' do
pod 'OneSignalXCFramework', '>= 5.0.0', '< 6.0'
end
```
```ruby Example theme={null}
target 'MyApp' do
config = use_native_modules!
use_react_native!(
:path => config[:reactNativePath],
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
post_install do |installer|
# https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
react_native_post_install(
installer,
config[:reactNativePath],
:mac_catalyst_enabled => false,
# :ccache_enabled => true
)
end
end
target 'OneSignalNotificationServiceExtension' do
pod 'OneSignalXCFramework', '>= 5.0.0', '< 6.0'
end
```
`Podfile` 상단에 `platform :ios, '11.0'`이 있는지 확인하세요. - 또는 앱에 필요한 경우 더 최신 iOS 버전을 사용하세요.
```Text Podfile theme={null}
# Uncomment this line to define a global platform for your project
platform :ios, '11.0'
```
터미널을 열고 `ios` 디렉터리로 `cd`한 다음 `pod install`을 실행합니다.
아래 오류가 표시되면 podfile 상단에 `use_frameworks!`를 추가하고 다시 시도하세요.
```
- Runner (true) and OneSignalNotificationServiceExtension (false) do not both set use_frameworks!.
```
#### OneSignalNotificationServiceExtension 코드
Xcode 프로젝트 네비게이터에서 **OneSignalNotificationServiceExtension 폴더**를 선택하고 `NotificationService.m` 또는 `NotificationService.swift` 파일을 엽니다.
전체 파일의 내용을 다음 코드로 교체합니다.
```swift Swift theme={null}
import UserNotifications
import OneSignalExtension
class NotificationService: UNNotificationServiceExtension {
var contentHandler: ((UNNotificationContent) -> Void)?
var receivedRequest: UNNotificationRequest!
var bestAttemptContent: UNMutableNotificationContent?
override func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {
self.receivedRequest = request
self.contentHandler = contentHandler
self.bestAttemptContent = (request.content.mutableCopy() as? UNMutableNotificationContent)
if let bestAttemptContent = bestAttemptContent {
/* DEBUGGING: Uncomment the 2 lines below to check this extension is executing
Note, this extension only runs when mutable-content is set
Setting an attachment or action buttons automatically adds this */
// print("Running NotificationServiceExtension")
// bestAttemptContent.body = "[Modified] " + bestAttemptContent.body
OneSignalExtension.didReceiveNotificationExtensionRequest(self.receivedRequest, with: bestAttemptContent, withContentHandler: self.contentHandler)
}
}
override func serviceExtensionTimeWillExpire() {
// Called just before the extension will be terminated by the system.
// Use this as an opportunity to deliver your "best attempt" at modified content, otherwise the original push payload will be used.
if let contentHandler = contentHandler, let bestAttemptContent = bestAttemptContent {
OneSignalExtension.serviceExtensionTimeWillExpireRequest(self.receivedRequest, with: self.bestAttemptContent)
contentHandler(bestAttemptContent)
}
}
}
```
```c objective-c theme={null}
#import
#import "NotificationService.h"
@interface NotificationService ()
@property (nonatomic, strong) void (^contentHandler)(UNNotificationContent *contentToDeliver);
@property (nonatomic, strong) UNNotificationRequest *receivedRequest;
@property (nonatomic, strong) UNMutableNotificationContent *bestAttemptContent;
@end
@implementation NotificationService
- (void)didReceiveNotificationRequest:(UNNotificationRequest *)request withContentHandler:(void (^)(UNNotificationContent * _Nonnull))contentHandler {
self.receivedRequest = request;
self.contentHandler = contentHandler;
self.bestAttemptContent = [request.content mutableCopy];
/* DEBUGGING: Uncomment the 2 lines below and comment out the one above to ensure this extension is executing
Note, this extension only runs when mutable-content is set
Setting an attachment or action buttons automatically adds this */
// NSLog(@"Running NotificationServiceExtension");
// self.bestAttemptContent.body = [@"[Modified] " stringByAppendingString:self.bestAttemptContent.body];
[OneSignalExtension didReceiveNotificationExtensionRequest:self.receivedRequest
withMutableNotificationContent:self.bestAttemptContent
withContentHandler:self.contentHandler];
}
- (void)serviceExtensionTimeWillExpire {
// Called just before the extension will be terminated by the system.
// Use this as an opportunity to deliver your "best attempt" at modified content, otherwise the original push payload will be used.
[OneSignalExtension serviceExtensionTimeWillExpireRequest:self.receivedRequest withMutableNotificationContent:self.bestAttemptContent];
self.contentHandler(self.bestAttemptContent);
}
@end
```
***
## 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.
If you are testing with an Android emulator, it should start with a cold boot.
1. Go to **Device Manager** in Android Studio.
2. Select your emulator device and click **Edit**.
3. Go to **Additional Settings** or **More**.
4. Set the **Boot option** to **Cold Boot**.
5. Save changes and restart the emulator.
### Check mobile subscriptions
The native push permission prompt should appear automatically if you added the `requestPermission` method during initialization.
Before accepting the prompt, check the OneSignal dashboard:
* Go to **Audience > Subscriptions**.
* You should see a new entry with the status "Never Subscribed".
The subscription's status should now show **Subscribed**.
You have successfully created a [mobile subscription](/docs/en/subscriptions).
Mobile subscriptions are created when users first open your app on a device or if they uninstall and reinstall your app on the same device.
### Set up test users
test users are helpful for testing a push notification before sending a message.
In the dashboard, next to the subscription, click the **Options (three dots)** button and select **Add to Test Users**.
Name the subscription so you can easily identify your device later in the **test users tab**.
Go to **Audience > Segments > New Segment**.
Name the segment `Test Users` (the name is important because it will be used later).
You have successfully created a segment of test users.
We can now test sending messages to this individual device and groups of test users.
### Send test push via API
In your OneSignal dashboard, go to **Settings > [Keys & IDs](/docs/en/keys-and-ids)**.
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"
],
"ios_attachments": {
"onesignal_logo": "https://avatars.githubusercontent.com/u/11823027?s=200&v=4"
},
"big_picture": "https://avatars.githubusercontent.com/u/11823027?s=200&v=4"
}'
```
Run the code in your terminal.
If all setup steps were completed successfully, the test users should receive a notification with an image included:
Images will appear small in the collapsed notification view. Expand the notification to see the full image.
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.
You have successfully sent a notification via our API to a segment.
* No image received? Your [Notification Service Extension](#ios-setup) might be missing.
* No confirmed receipt? Review the troubleshooting guide [here](/docs/en/confirmed-delivery#troubleshooting-confirmed-delivery).
* Having issues? Copy-paste the api request and a log from start to finish of app launch into a `.txt` file. Then share both with `support@onesignal.com`.
### Send an in-app message
[In-app messages](/docs/en/in-app-messages-setup) let you communicate with users while they are using your app.
This is because users must meet the in-app audience criteria *before* a new session starts. In OneSignal, a new session starts when the user opens your app after it has been in the background or closed for at least 30 seconds. For more details, see our guide on [how in-app messages are displayed](/docs/en/in-app-messages-setup#how-are-iams-displayed%3F).
* 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.
Under **Schedule > How often do you want to show this message?** select **Every time trigger conditions are satisfied**.
Click **Make Message Live** so it is available to your Test Users each time they open the app.
After the in-app message is live, open your app. You should see it display:
Not seeing the message?
* 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](/docs/en/in-app-messages-setup#how-are-iams-displayed%3F).
* Still in the `Test Users` segment?
* If you reinstalled or switched devices, re-add the device to [Test Users](#set-up-test-users) and confirm it's part of the Test Users segment.
* Having issues?
* Follow [Getting a Debug Log](/docs/en/capturing-a-debug-log) while reproducing the steps above. This will generate additional logging that you can share with `support@onesignal.com` and we will help investigate what's going on.
You have successfully setup the OneSignal SDK and learned important concepts like:
* Gathering [Subscriptions](/docs/en/subscriptions), setting [Test Users](/docs/en/find-set-test-subscriptions), and creating [Segments](/docs/en/segmentation).
* Sending [Push](/docs/en/push) with images and [Confirmed receipt](/docs/en/confirmed-delivery) using Segments and our [Create message](/reference/create-message) API.
* Sending [In-app messages](/docs/en/in-app-messages-setup).
Continue with this guide to identify users in your app and setup additional features.
***
## User identification
Previously, we demonstrated how to create mobile [Subscriptions](/docs/en/subscriptions). Now we'll expand to identifying [Users](/docs/en/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](/docs/en/integrations)).
Set the External ID with our SDK's [`login` method](/docs/en/mobile-sdk-reference#login-external-id) each time they are identified by your app.
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 our SDK is highly recommended to identify users across all their subscriptions, regardless of how they are created.
### 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 our SDK [`addTag` and `addTags` methods](/docs/en/mobile-sdk-reference#data-tags) 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`.
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:
### 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 [`addEmail` method](/docs/en/mobile-sdk-reference#addemail-%2C-removeemail) to create email subscriptions.
* Use the [`addSms` method](/docs/en/mobile-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).
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.
***
### Privacy & user consent
To control when OneSignal collects user data, use the SDK's consent gating methods:
* [`setConsentRequired(true)`](/docs/en/mobile-sdk-reference#setconsentrequired): Prevents data collection until consent is given.
* [`setConsentGiven(true)`](/docs/en/mobile-sdk-reference#setconsentgiven): Enables data collection once consent is granted.
See our Privacy & security docs for more on:
* [Data collected by the SDK](/docs/en/data-collected-by-the-onesignal-sdk)
* [Handling personal data](/docs/en/handling-personal-data)
***
## Prompt for push permissions
Instead of calling `requestPermission()` 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](/docs/en/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](/docs/en/mobile-sdk-reference) for more details.
### Push notification events
* [`addClickListener()`](/docs/en/mobile-sdk-reference#addclicklistener-push): Detect when a notification is tapped. Helpful for [Deep Linking](/docs/en/deep-linking).
* [`addForegroundLifecycleListener()`](/docs/en/mobile-sdk-reference#addforegroundlifecyclelistener-push): Control how notifications behave in foreground.
For full customization, see [Mobile Service Extensions](/docs/en/service-extensions).
### User state changes
* [`addObserver()` for user state](/docs/en/mobile-sdk-reference#addobserver-user-state): Detect when the External ID is set.
* [`addPermissionObserver()`](/docs/en/mobile-sdk-reference#addpermissionobserver-push): Track the user's specific interaction with the native push permission prompt.
* [`addObserver()` for push subscription](/docs/en/mobile-sdk-reference#addobserver-push-subscription-changes): Track when the push subscription status changes.
### In-app message events
* [`addClickListener()`](/docs/en/mobile-sdk-reference#addclicklistener-in-app): Handle in-app click actions. Ideal for deep linking or tracking events.
* [`addLifecycleListener()`](/docs/en/mobile-sdk-reference#addclicklistener-in-app): 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](/docs/en/migrating-to-onesignal)
* [🌍 Location tracking](/docs/en/mobile-sdk-reference#location)
* [🔗 Deep Linking](/docs/en/deep-linking)
* [🔌 Integrations](/docs/en/integrations)
* [🧩 Mobile Service Extensions](/docs/en/service-extensions)
* [🛎️ Action buttons](/docs/en/action-buttons)
* [🌐 Multi-language messaging](/docs/en/multi-language-messaging)
* [🛡️ Identity Verification](/docs/en/identity-verification)
* [📊 Custom Outcomes](/docs/en/custom-outcomes)
* [📲 Live Activities](/docs/en/live-activities)
### Mobile SDK setup & reference
Make sure you've enabled all key features by reviewing the [Mobile push setup](/docs/en/mobile-push-setup) guide.
For full details on available methods and configuration options, visit the [Mobile SDK reference](/docs/en/mobile-sdk-reference).
Congratulations! You've successfully completed the Mobile SDK setup guide.
***
***