OneSignal Huawei SDK Setup Guide for Android Studio.
Step-by-step instructions for configuring your OneSignal app.
Create or select your app
Example shows creating a new app.
Set up and activate a platform
Example setting up your first OneSignal app, org, and channel.
Configure platform credentials
Choose target SDK
Select which SDK you are using to be navigated to the docs.
Install SDK and save your App ID
Save your App ID and invite additional team members.
agconnect-services.json
in your Android Studio Project from setting up a different Huawei service.SHA-256
for your release
variant.
SHA-256
for your debug
variant too.build.gradle
(Project: ) in Android Studio and add maven {url 'https://developer.huawei.com/repo/'}
under buildscript { repositories }
and allprojects { repositories }
Under buildscript { dependencies }
add classpath 'com.huawei.agconnect:agcp:1.6.5.300'
You should have in total 3 new lines in your root build.gradle
, highlighted below.
app/build.gradle
file and add implementation 'com.huawei.hms:push:6.3.0.304' under the
dependencies` section.
Also to the app/build.gradle
file add apply plugin: 'com.huawei.agconnect'
to the very bottom of the file.
You should have in total 2 new lines in your app/build.gradle
, highlighted below.
HmsMessageService
classHmsMessageService
More details...
HmsMessageService
, if you donβt have one already and add the following methods.HmsMessageService
please add the two
new OneSignalHmsEventBridge
lines instead of creating another class.onNewToken
and onMessageReceived
to OneSignal via the OneSignalHmsEventBridge
.If you didnβt have a class that extended HmsMessageService
before make sure to add it to your AndroidManifest.xml
under the <application>
tag.More details...
exclude
with implementation
in your app/build.gradle
.More details...
AndroidManifest.xml
:6003 error
debug
or release
) so that a 6003
error is avoided when registering for Huawei pushToken
with the OneSignal SDK. See βConfigure a Signatureβ sectionnotification_types: -25
"notification_types":-25
means OneSignal timed out waiting for a response from Huaweiβs HMS to get a push token. This is most likely due to another 3rd-party HMS push SDK or your own HmsMessageService getting this event instead of OneSignal.Please review step on how to check this and forward the event if this is the case.notification_types: -28
com.huawei.hms:push
in the build.gradle
will cause this specific error not to happen any more. However, if you have some aggressive Proguard or R8 settings, this might cause issues. We recommend turn off minifyEnabled
temporary if you have it to see if that is the root of the issue.Also, you shouldnβt mix and match major release versions of other HMS libraries. Start with either 4 or 5. Make sure not to have a mixture from 3 to 5 which is going to create other errorsError getting Huawei push token
Launch your app on a test device.
requestPermission
method during initialization.iOS and Android push permission prompts
Check your OneSignal dashboard
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
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
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
.txt
file. Then share both with support@onesignal.com
.Close or background your app on the device.
Create an in-app message.
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
Test Users
segment?
support@onesignal.com
and we will help investigate whatβs going on.login
method each time they are identified by your app.
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"
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
addEmail
method to create email subscriptions.addSms
method to create SMS subscriptions.A user profile with push, email, and SMS subscriptions unified by External ID
setConsentRequired(true)
: Prevents data collection until consent is given.setConsentGiven(true)
: Enables data collection once consent is granted.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.
addClickListener()
: Detect when a notification is tapped. Helpful for Deep Linking.addForegroundLifecycleListener()
: Control how notifications behave in foreground.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.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.).support@onesignal.com
Please include: