Flutterflow SDK setup

This guide is for Flutterflow mobile app setup. If you have a Flutterflow site, please see our Web SDK setup guide.

Requirements

Flutterflow plan: Standard or higher
Configured OneSignal app and platform

iOS Requirements

macOS with Xcode 14+ (setup instructions use Xcode 16.2)
Device with iOS 12+, iPadOS 12+, or Xcode simulator running iOS 16.2+
CocoaPods 1.16.2+

Android Requirements

Android 7.0+ device or emulator with Google Play Store (Services) installed

Configure your OneSignal app and platform

Configure your OneSignal app with the platforms you support — Apple (APNs), Google (FCM), Huawei (HMS), and/or Amazon (ADM).

If your organization already has a OneSignal account, ask to be invited to the Organization. Otherwise, sign up for a free account to get started.

Step-by-step setup instructions

Create or select your app

Create a new app by clicking New App/Website, or add a platform to an existing app in Settings > Push & In-App. Select the platform(s) you want to configure and click Next: Configure Your Platform.

OneSignal dashboard showing the new app setup flow with Organization name, app name, and channel selection

Configure platform credentials

Enter the credentials for your platform:

Android: Set up Firebase credentials
iOS: p8 token (recommended) or p12 certificate
Amazon: Generate API key
Huawei: Authorize OneSignal

Click Save & Continue after entering your credentials.

Save your App ID and install the SDK

Your App ID is displayed on the final screen. Copy and save it — you need it when initializing the SDK. Select your SDK platform, then follow the setup guide.

Setup

1. Create a new custom action

In your Flutterflow project, navigate to Custom Code, then click the +Add button and select Action.

Under Action settings on the right-hand toolbar, click Add Dependency and enter the following dependency and click refresh to add it to the action:

dependency

  dependencies:
  	onesignal_flutter: ^5.1.2

In the Action Code, under the pre-loaded code add the following, then save and compile your action. Replace YOUR_APP_ID with your OneSignal App ID found in your OneSignal dashboard Settings > Keys & IDs.

If you don’t have access to the OneSignal app, ask your Team Members to invite you.

Flutter

  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);
  }

Next, click on the main.dart file in the left-hand tool bar and click the + icon next to Initial Actions in the right-hand bar and click on the onesignal action that has just been created.

This will add the action to you app and cause the OneSignal SDK to be initialised when the app runs:

2. Exporting the project

APK download (Android only)
Full project download (iOS and Android)

Open the Developer Menu and download the APK:

Once the APK has downloaded, you can test the app by dragging the APK into an Android emulator to install it. Push capabilities should work immediately and you can send push notifications to the device as soon as you provide push permissions through the native prompt.

3. iOS Setup

The downloaded project will likely not be ready to launch in iOS. Before setting up the OneSignal specific additions, you will need to make sure that the project is fully built. To do so:

Open up a Terminal window, cd (change directory) to the ios folder of your downloaded project.
In Terminal type flutter build iosand press enter. Wait for the build to complete, this may take some time depending on the size of your project.
Still in Terminal type pod install and press enter. Wait for the pod install to complete.

Open the .xcworkspace file in Xcode located your project’s ios folder. Select the root project > your main app target > Signing & Capabilities. If you do not see Push Notifications enabled, click + Capability and add Push Notifications. Ensure that you enter the correct details for your Team and Bundle Identifier.

Click + Capability again and add Background Modes. Then check Remote notifications.

Add Notification Service Extension

The OneSignalNotificationServiceExtension allows your iOS application to receive rich notifications with images, buttons, and badges. It’s also required for OneSignal’s Confirmed Delivery analytics features. In Xcode Select File > New > Target… Select Notification Service Extension then Next.

Enter the product name as OneSignalNotificationServiceExtension and press Finish.

Do not activate the scheme on the dialog that is shown after selecting Finish. Press Cancel on the “Activate scheme” prompt.

Select the OneSignalNotificationServiceExtension target and General settings. Set Minimum Deployments to be the same value as your Main Application Target. This should be iOS 11 or higher.

Add App Groups

App Groups allow your app and the OneSignalNotificationServiceExtension to communicate when a notification is received, even if your app is not active. This is required for badges and Confirmed Deliveries. Select your Main App Target > Signing & Capabilities > + Capability > App Groups.

Within App Groups, click the + button. Set the App Groups container to be group.YOUR_BUNDLE_IDENTIFIER.onesignal where YOUR_BUNDLE_IDENTIFIER is the same as your Main Application “Bundle Identifier”.

Press OK and repeat for the OneSignalNotificationServiceExtension Target. Select the OneSignalNotificationServiceExtension Target > Signing & Capabilities > + Capability > App Groups.

Within App Groups, click the + button. Set the App Groups container to be group.YOUR_BUNDLE_IDENTIFIER.onesignal where YOUR_BUNDLE_IDENTIFIER is the same as your Main Application “Bundle Identifier”. DO NOT INCLUDE OneSignalNotificationServiceExtension.

Optional instructions to setup custom App Group Name

This step is only required if you do not want to use the default app group name (which is group.{your_bundle_id}.onesignal).Open your Info.plist file and add a new OneSignal_app_groups_key as a String type.Enter the group name you checked in the last step as it’s value.Make sure to do the same for the Info.plist under the OneSignalNotificationServiceExtension folder.

Add OneSignal SDK to the OneSignalNotificationServiceExtension

Update your ios/Podfile to include:

target 'OneSignalNotificationServiceExtension' do
  pod 'OneSignalXCFramework', '>= 5.0.0', '< 6.0'
end

At the top of your Podfile make sure you have platform :ios, '11.0'. - Or a newer iOS version if your app requires it.

# Uncomment this line to define a global platform for your project
platform :ios, '11.0'

Open terminal, cd to the ios directory, and run pod install. If you see the error below, add use_frameworks! to the top of your podfile and try again.

- Runner (true) and OneSignalNotificationServiceExtension (false) do not both set use_frameworks!.

OneSignalNotificationServiceExtension Code

In the Xcode project navigator, select the OneSignalNotificationServiceExtension folder and open the NotificationService.m or NotificationService.swift file. Replace the whole file’s contents with the following code.

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)
        }
    }
}

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.

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.

The native push permission prompt should appear automatically if you added the requestPermission method during initialization.

Check your OneSignal dashboard

Before accepting the prompt, check the OneSignal dashboard:

Go to Audience > Subscriptions.
You should see a new entry with the status “Never Subscribed”.

Return to the app and tap Allow on the prompt.

Refresh the OneSignal dashboard Subscription's page.

The subscription’s status should now show Subscribed.

You have successfully created a mobile subscription. 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 subscriptions

Test subscriptions are helpful for testing a push notification before sending a message.

Add to Test Subscriptions.

In the dashboard, next to the subscription, click the Options (three dots) button and select Add to Test Subscriptions.

Name your subscription.

Name the subscription so you can easily identify your device later in the Test Subscriptions tab.

Create a test users segment.

Go to Audience > Segments > New Segment.

Name the 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.

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

Get your App API Key and App ID.

In your OneSignal dashboard, go to Settings > Keys & IDs.

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 -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.

Run the code in your terminal.

Check images and confirmed delivery.

If all setup steps were completed successfully, the test subscriptions 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.

Check for confirmed delivery.

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.

If you’re on a Professional plan or higher, scroll to Audience Activity to see subscription-level confirmation:

You have successfully sent a notification via our API to a segment.

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 .txt file. Then share both with support@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.

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.

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.

Customize the message content if desired.

Set Trigger to 'On app open'.

Schedule frequency.

Under Schedule > How often do you want to show this message? select Every time trigger conditions are satisfied.

Make message live.

Click Make Message Live so it is available to your Test Users each time they open the app.

Open the app and see the message.

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.
Still in the Test Users segment?
- 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.com and we will help investigate what’s going on.

You have successfully setup the OneSignal SDK and learned important concepts like:

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.

Continue with this guide to identify users in your app and setup additional features.

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’s login method 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 data tags

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 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.

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 to create email subscriptions.
Use the addSms method 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.

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.

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.

See our Privacy & security docs for more on:

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 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.

For full customization, see Mobile Service Extensions.

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:

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.

Congratulations! You’ve successfully completed the Mobile SDK setup guide.

Developer Documentation

Mobile SDKs

Web SDKs

Live Activities

Desktop & Watch Setup

Legacy SDK reference

Flutterflow SDK setup

Requirements

Configure your OneSignal app and platform

Setup

1. Create a new custom action

2. Exporting the project

3. iOS Setup

Add Notification Service Extension

Add App Groups

Add OneSignal SDK to the OneSignalNotificationServiceExtension

OneSignalNotificationServiceExtension Code

Testing the OneSignal SDK integration

Check mobile subscriptions

Set up test subscriptions

Send test push via API

Send an in-app message

User identification

Assign External ID

Add data tags

Add email and/or SMS subscriptions

Prompt for push permissions

Listen to push, user, and in-app events

Push notification events

User state changes

In-app message events

Advanced setup & capabilities

Mobile SDK setup & reference

Developer Documentation

Mobile SDKs

Web SDKs

Live Activities

Desktop & Watch Setup

Legacy SDK reference

​Requirements

​Configure your OneSignal app and platform

​Setup

​1. Create a new custom action

​2. Exporting the project

​3. iOS Setup

​Add Notification Service Extension

​Add App Groups

​Add OneSignal SDK to the OneSignalNotificationServiceExtension

​OneSignalNotificationServiceExtension Code

​Testing the OneSignal SDK integration

​Check mobile subscriptions

​Set up test subscriptions

​Send test push via API

​Send an in-app message

​User identification

​Assign External ID

​Add data tags

​Add email and/or SMS subscriptions

​Privacy & user consent

​Prompt for push permissions

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

​Push notification events

​User state changes

​In-app message events

​Advanced setup & capabilities

​Mobile SDK setup & reference

Requirements

Configure your OneSignal app and platform

Setup

1. Create a new custom action

2. Exporting the project

3. iOS Setup

Add Notification Service Extension

Add App Groups

Add OneSignal SDK to the OneSignalNotificationServiceExtension

OneSignalNotificationServiceExtension Code

Testing the OneSignal SDK integration

Check mobile subscriptions

Set up test subscriptions

Send test push via API

Send an in-app message

User identification

Assign External ID

Add data tags

Add email and/or SMS subscriptions

Privacy & user consent

Prompt for push permissions

Listen to push, user, and in-app events

Push notification events

User state changes

In-app message events

Advanced setup & capabilities

Mobile SDK setup & reference