Skip to main content

​
Visão Geral

Este guia explica como integrar notificações push do OneSignal em uma aplicação Flutter distribuída na Huawei AppGallery. Siga estas instruções apenas se seu aplicativo for distribuído na Huawei AppGallery.

​
Requisitos

  • Android Studio
  • Um dispositivo Huawei com “Huawei App Gallery” instalado
  • Aplicativo e Plataforma OneSignal configurados

​
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.
You can manage multiple platforms (iOS, Android, Huawei, Amazon, Web) under a single OneSignal app.
1

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

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

Configure platform credentials

Follow the prompts based on your platforms:Click Save & Continue after entering your credentials.
4

Choose target SDK

Select the SDK that matches your development platform (e.g., iOS, Android, React Native, Unity), then click Save & Continue.
5

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.
Once complete, follow the SDK installation guide for your selected platform to finish integrating OneSignal.

​
Configuração

​
1. Configurar o SDK do OneSignal

Configuração do SDK OneSignal Flutter

Siga o guia de configuração do SDK OneSignal Flutter para implementar nosso SDK em seu aplicativo. Observe que a configuração Firebase/Google não é necessária para builds de aplicativos lançados na Huawei AppGallery.

​
2. Configuração Huawei

Configure as Informações do Aplicativo no AppGallery Connect. Veja Configure App Information in AppGallery Connect da Huawei Adicione dependências ao projeto android do Flutter. No build.gradle do projeto adicione o seguinte
Se estiver usando o Flutter Huawei Plugin, pule para a etapa 3
buildscript {
    repositories {
        google()
        maven { url 'http://developer.huawei.com/repo/' }
    }

    dependencies {
        ...
        classpath 'com.huawei.agconnect:agcp:1.6.5.300'
    }
}

allprojects {
    repositories {
        google()
        maven { url 'http://developer.huawei.com/repo/' }
    }
}
No app build.gradle adicione o seguinte 
dependencies {
    ...
    implementation 'com.huawei.hms:push:6.3.0.304'
}

apply plugin: 'com.huawei.agconnect'

​
Etapas de configuração adicionais

​
Configuração do plugin Flutter Huawei (opcional)

O OneSignal não requer o plugin Flutter Huawei e na maioria dos casos você pode omitir isso. No entanto, se você precisar de recursos específicos da Huawei no Flutter, veja Integrating Flutter HMS Push Kit Module Ao seguir a configuração do plugin, após baixar o plugin, remova o FlutterHMSMessageService do arquivo AndroidManifest.xml do plugin baixado sob o pacote android.

​
Serviço de localização Huawei (opcional)

Adicione implementation 'com.huawei.hms:location:<HUAWEI HMS VERSION #> à seção dependencies do build.gradle do seu aplicativo. Certifique-se também de adicionar a permissão de localização ao seu AndroidManifest.xml se você ainda não tiver isso 
dependencies {
    ...
    implementation 'com.huawei.hms:location:4.0.0.300'
}

​
Solução de problemas Huawei

Durante os testes, certifique-se de manter o método OneSignal setLogLevel definido como VERBOSE. Verifique os logs para ver quaisquer erros sendo lançados e Códigos de Erro Comuns do Huawei.
Você pode precisar criar uma assinatura de keystore de debug ou release (escolha o caminho de build do app correto, debug ou release) para que um erro 6003 seja evitado ao registrar para o pushToken da Huawei com o SDK OneSignal. Veja a seção “Configure a Signature”
Isso significa que há uma classe que o HMS está faltando no aplicativo que é necessária para push. Apenas ter com.huawei.hms:push no build.gradle fará com que este erro específico não aconteça mais. No entanto, se você tiver algumas configurações agressivas de Proguard ou R8, isso pode causar problemas. Recomendamos desativar minifyEnabled temporariamente se você tiver isso para ver se essa é a raiz do problema.Além disso, você não deve misturar versões de lançamento principais de outras bibliotecas HMS. Comece com 4 ou 5. Certifique-se de não ter uma mistura de 3 a 5, o que criará outros erros
E/OneSignal: HMS ApiException getting Huawei push token!
    com.huawei.hms.common.ApiException: -5: Core error
Verifique suas regras de Proguard ou R8 para garantir que estejam configuradas corretamente. Possivelmente desative-o temporariamente para ver se está relacionado. Se corrigir o problema após desativar o Proguard ou R8, você pode seguir este guia e ativá-lo novamente. Veja a seção “Configure a Signature”

​
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

1

Launch your app on a test device.

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

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

Return to the app and tap Allow on the prompt.

4

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

Add to Test Subscriptions.

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

Name your subscription.

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

Create a test users segment.

Go to Audience > Segments > New Segment.
4

Name the segment.

Name the segment Test Users (the name is important because it will be used later).
5

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

1

Get your App API Key and App ID.

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

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"
}'
3

Run the code.

Run the code in your terminal.
4

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

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 [email protected].

​
Send an in-app message

In-app messages let you communicate with users while they are using your app.
1

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

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

Customize the message content if desired.

4

Set Trigger to 'On app open'.

5

Schedule frequency.

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

Make message live.

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

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 [email protected] and we will help investigate what’s going on.
You have successfully setup the OneSignal SDK and learned important concepts like: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. 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: 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

For full customization, see Mobile Service Extensions.

​
User state changes

​
In-app message events

​
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.
Need help?Chat with our Support team or email [email protected]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!