.NET MAUI SDK setup
Instructions for adding OneSignal .NET SDK to your cross-platform MAUI app for iOS, Android, and Desktop.
Overview
This guide explains how to integrate OneSignal push notifications into a .NET MAUI application. It covers everything from installation to configuration and service worker management.
Requirements
- .NET 7.0+
- Visual Studio 2019 or newer
- 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
Required setup for push notifications
To start sending push notifications with OneSignal, you must first configure your OneSignal app with all the platforms your support—Apple (APNs), Google (FCM), Huawei (HMS), and/or Amazon (ADM).
If your organization already has a OneSignal account, ask to be invited as an admin role to configure the app. Otherwise, sign up for a free account to get started.
Step-by-step instructions for configuring your OneSignal app.
Step-by-step instructions for configuring your OneSignal app.
You can manage multiple platforms (iOS, Android, Huawei, Amazon, Web) under a single OneSignal app.
Create or select your app
- To add platforms to an existing app, go to Settings > Push & In-App in the OneSignal dashboard.
- To start fresh, click New App/Website and follow the prompts.
Example shows creating a new app.
Set up and activate a platform
- Choose a clear and recognizable name for your app and organization.
- Select the platform(s) you want to configure (iOS, Android, etc.).
- Click Next: Configure Your Platform.
Example setting up your first OneSignal app, org, and channel.
Configure platform credentials
Follow the prompts based on your platforms:
- 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.
Choose target SDK
Select the SDK that matches your development platform (e.g., iOS, Android, React Native, Unity), then click Save & Continue.
Select which SDK you are using to be navigated to the docs.
Install SDK and save your App ID
Once your platform is configured, your OneSignal App ID will be displayed. Copy and save this ID—you’ll need it when installing and initializing the SDK.
If collaborating with others, use the Invite button to add developers or teammates, then click Done to complete setup.
Save your App ID and invite additional team members.
Once complete, follow the SDK installation guide for your selected platform to finish integrating OneSignal.
SDK Setup
1. Add SDK
Using the .NET CLI:
2. Initialize SDK
Initialize OneSignal in App.xaml.cs
file.
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.
3. Adding an iOS Service Extension
Microsoft has a guide on generating a Notification Service Extension here, using Visual Studio and Visual Studio for Mac, but does not have any guidance on how you would create this for VSCode at this time.
If you generate a service extension following the guide above, you can follow this the code in our sample project found on Github
Android setup
Make sure your OneSignal app is configured for the Android platform using your Firebase credentials.
Set up your notification icons to match your app’s branding. If this step is skipped, a default bell icon will display for your push notifications.
Build for Android
At this point, you should be able to build and run your app on a physical Android device or emulator without issues.
After confirming that your Android build works:
- Continue with the iOS setup, if applicable.
- Or jump ahead to Testing the OneSignal SDK integration.
iOS setup
Make sure your OneSignal app is configured for the iOS platform using either the p8 Token (Recommended) or p12 Certificate.
Follow these steps to add push notifications to your iOS app, including support for Badges, Confirmed Delivery, and images.
1. Add Push Notifications capability to app target
The Push Notifications capability allows your app to register a push token and receive notifications.
- Open your app’s
.xcworkspace
file in Xcode. - Select your app target > Signing & Capabilities
- Click + Capability and add Push Notifications capability
The app target is given Push Notifications capability.
2. Add Background Modes capability to app target
This enables your app to wake in the background when push notifications arrive.
- Add Background Modes capability
- Enable Remote notifications
The app target is given Remote Notifications background execution mode.
3. Add app target to App Group
App Groups allow data sharing between your app and the Notification Service Extension. Required for Confirmed Delivery and Badges.
- Add App Groups capability
- In the App Groups capability click +
- Add a new container ID in format:
group.your_bundle_id.onesignal
- Keep group. and .onesignal prefix and suffix. Replace
your_bundle_id
with your app’s bundle identifier. - For example, bundle identifier
com.onesignal.MyApp
, will have the container namegroup.com.onesignal.MyApp.onesignal
.
The app target is part of the App Group.
- Add App Groups capability
- In the App Groups capability click +
- Add a new container ID in format:
group.your_bundle_id.onesignal
- Keep group. and .onesignal prefix and suffix. Replace
your_bundle_id
with your app’s bundle identifier. - For example, bundle identifier
com.onesignal.MyApp
, will have the container namegroup.com.onesignal.MyApp.onesignal
.
The app target is part of the App Group.
- Open your app’s
Info.plist
- Add a new property:
- Key:
OneSignal_app_groups_key
- Value: Your existing App Group name (e.g.,
group.com.example.mycustomgroup
)
Custom app group set inside the app target.
4. Add Notification Service Extension
The Notification Service Extension (NSE) enables rich notifications and Confirmed Delivery analytics.
- In Xcode: File > New > Target…
- Select Notification Service Extension, then Next.
- Set the product name to
OneSignalNotificationServiceExtension
and press Finish. - Press Don’t Activate on the Activate scheme prompt.
Select the Notification Service Extension target.
Name the Notification Service Extension .
Cancel activation to continue debugging your app target.
Set the OneSignalNotificationServiceExtension Minimum Deployment Target to match your main app (iOS 15+ recommended).
Set the same deployment target as the main app.
5. Add NSE target to app group
Use the same App Group ID you added in step 3.
- Go to OneSignalNotificationServiceExtension > Signing & Capabilities
- Add App Groups
- Add the exact same group ID
The NSE now belongs to the same app group as your app target.
6. Update NSE code
- Navigate to the OneSignalNotificationServiceExtension folder
- Replace the contents of the
NotificationService.swift
orNotificationService.m
file with the following:
Navigate to your NotificationService file.
You should see an error because the OneSignal package is not installed. This will be resolved in the next step.
This file shows an error until you install the package in the next step.
7. Add OneSignal to the NSE target
Update your ios/Podfile
to include:
Open your project in the terminal and run:
Common pod install errors
You may run into the following errors, here is how you can resolve them.
ArgumentError - \[Xcodeproj] Unable to find compatibility version string for
object version `70`.
ArgumentError - \[Xcodeproj] Unable to find compatibility version string for object version `70`.
CocoaPods relies on the xcodeproj
Ruby gem to read your Xcode project files. As of now, the latest xcodeproj
release does not recognize object version 70, which was introduced by Xcode 16. So when CocoaPods tries to open your .xcodeproj
file, it crashes with this error.
- Close Xcode.
- Navigate to your project’s
ios/<your-app>.xcodeproj/project.pbxproj
file. - Change this line:
objectVersion = 70;
- Replace it with:
objectVersion = 55;
- Save, close, and rerun
cd ios pod install cd ..
Build for iOS
You should now be able to build and run your app on a real iOS device or iOS simulator (16.2+).
Common iOS build errors
Cycle Inside... building could produce unreliable results.
Cycle Inside... building could produce unreliable results.
You may see this error when building with Xcode 15+, due to a default configuration change affecting cross platform systems.
- Open your
.xcworkspace
folder in Xcode and navigate to your app target > Build Phases. - You should have a phase called “Embed Foundation Extensions” or “Embed App Extensions”.
- Drag and move this build phase to above “Run Script”.
- Build and run your app. The error should be resolved.
Correct order of Build Phases in Xcode.
Uncheck Copy only when installing.
PBXGroup Error
PBXGroup Error
RuntimeError - PBXGroup
attempted to initialize an object with unknown ISA PBXFileSystemSynchronizedRootGroup
from attributes: {"isa"=>"...", "exceptions"=>["//", "..."], "explicitFileTypes"=>{}, "explicitFolders"=>[], "path"=>"OneSignalNotificationServiceExtension", "sourceTree"=>"<group>"}
Fix:
- Find the folder listed under “path” in the error
- In Xcode project sidebar, right-click the folder
- Select Convert to Group
Path error for PBXGroup.
Convert folder to group.
After confirming that your iOS build works, continue with Testing the OneSignal SDK integration.
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.
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.
iOS and Android push permission prompts
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”.
Dashboard showing subscription with 'Never Subscribed' status
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.
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.
In the dashboard, next to the subscription, click the Options (three dots) button and select Add to Test Subscriptions.
Adding a device to Test Subscriptions
Name your subscription.
Name the subscription so you can easily identify your device later in the Test Subscriptions tab.
Dashboard showing the 'Name your subscription' field
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.
Creating a 'Test Users' segment with the Test Users filter
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.
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:
Push notification with image on iOS and Android
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.
Delivery stats showing confirmed delivery
If you’re on a Professional plan or higher, scroll to Audience Activity to see subscription-level confirmation:
Confirmed delivery at the device level in Audience Activity
- No image received? Your Notification Service Extension might be missing.
- No confirmed delivery? Review your App Groups setup.
- Having issues? Copy-paste the api request and a log from start to finish of app launch into a
.txt
file. 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.
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.
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.
Under Schedule > How often do you want to show this message? select Every time trigger conditions are satisfied.
In-app message scheduling options
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:
Welcome in-app message shown on devices
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.
- Follow Getting a Debug Log while reproducing the steps above. This will generate additional logging that you can share with
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
.
A user profile in OneSignal with a tag called "current_level" set to "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:
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
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.
A user profile with push, email, and SMS subscriptions unified by External ID
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)
: 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:
- 🔁 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.
Need help?
Chat with our Support team or email support@onesignal.com
Please include:
- Details of the issue you’re experiencing and steps to reproduce if available
- Your OneSignal App ID
- The External ID or Subscription ID if applicable
- The URL to the message you tested in the OneSignal Dashboard if applicable
- Any relevant logs or error messages
We’re happy to help!