connector

Core library to subscribe and receive push notifications with UnifiedPush.

To receive notifications with UnifiedPush, users must have a dedicated application, a distributor, installed on their system.

This library requires Android 4.1 or higher.

Import the library

Add the dependency to the module build.gradle. Replace {VERSION} with the latest version.

dependencies {
    // ...
    implementation('org.unifiedpush.android:connector:{VERSION}')
}

The library depends on tink which may be used by another library you depend on. In this case, it is possible the build failed because of duplicate classes.

The conflict must be resolved in the module gradle file, after the plugins and android blocks:

Gradle Kotlin DSL

app/build.gradle.kts:

configurations.all {
    val tink = "com.google.crypto.tink:tink-android:1.17.0"
    // You can also use the library declaration catalog
    // val tink = libs.google.tink
    resolutionStrategy {
        force(tink)
        dependencySubstitution {
            substitute(module("com.google.crypto.tink:tink")).using(module(tink))
        }
    }
}

Content copied to clipboard

Gradle Groovy DSL

app/build.gradle:

configurations.all {
    def tink = "com.google.crypto.tink:tink-android:1.17.0"
    resolutionStrategy {
        force(tink)
        dependencySubstitution {
           substitute module('com.google.crypto.tink:tink') using module(tink)
        }
    }
}

Content copied to clipboard

Expose a Service to handle incoming events

You need to declare a service that extend PushService. This service must not be exported and must handle the action org.unifiedpush.android.connector.PUSH_EVENT:

<service android:name=".PushServiceImpl"
    android:exported="false">
    <intent-filter>
        <action android:name="org.unifiedpush.android.connector.PUSH_EVENT"/>
    </intent-filter>
</service>

Request registrations

Interactions with the distributor are done with the UnifiedPush object.

Use user's default distributor

Users are allowed to define a default distributor on their system, because UnifiedPush distributors have to be able to process a deeplink.

When you set UnifiedPush for the first time on your application, you will want to use the default user's distributor.

Therefore, you can use tryUseCurrentOrDefaultDistributor to select the saved distributor or the default one when the user enables UnifiedPush.

When the distributor is saved, you can call register to request a new registration. It has optional parameters, the following example uses messageForDistributor and vapid. You can use instance to bring multiple-registration support to your application.

import org.unifiedpush.android.connector.UnifiedPush
/* ... */

UnifiedPush.tryUseCurrentOrDefaultDistributor(context) { success ->
    if (success) {
        // We have a distributor
        // Register your app to the distributor
        UnifiedPush.register(context, messageForDistributor, vapid)
    }
}

import static org.unifiedpush.android.connector.ConstantsKt.INSTANCE_DEFAULT;
import org.unifiedpush.android.connector.UnifiedPush;
/* ... */

UnifiedPush.tryUseCurrentOrDefaultDistributor(context, success ->{
    if (success) {
        // We have a distributor
        // Register your app to the distributor
        UnifiedPush.register(
            context,
            INSTANCE_DEFAULT,
            messageForDistributor,
            vapid
        );
    }
});

Be aware that tryUseCurrentOrDefaultDistributor starts a new translucent activity in order to get the result of the distributor activity. You may prefer to use LinkActivityHelper directly in your own activity instead.

Use another distributor

The user may want to use another distributor: it can be achieved with tryPickDistributor.

Implement your own distributor picker

For this, you can get the list of available distributors with getDistributors.

Once the user has chosen the distributor, you have to save it with saveDistributor. This function must be called before register.

When the distributor is saved, you can call register to request a new registration. It has optional parameters, the following example uses messageForDistributor and vapid. You can use instance to bring multiple-registration support to your application.

import org.unifiedpush.android.connector.UnifiedPush
/* ... */

// Get a list of distributors that are available
val distributors = UnifiedPush.getDistributors(context)
// select one or ask the user which distributor to use, e.g. with a dialog
val userDistrib = yourFunc(distributors)
// save the distributor
UnifiedPush.saveDistributor(context, userDistrib)
// register your app to the distributor
UnifiedPush.register(context, messageForDistributor, vapid)

import static org.unifiedpush.android.connector.ConstantsKt.INSTANCE_DEFAULT;
import org.unifiedpush.android.connector.UnifiedPush;
/* ... */

// Get a list of distributors that are available
List<String> distributors = UnifiedPush.getDistributors(context);
// select one or show a dialog or whatever
String userDistrib = yourFunc(distributors);
// the below line will crash the app if no distributors are available
UnifiedPush.saveDistributor(context, userDistrib);
UnifiedPush.register(
    context,
    INSTANCE_DEFAULT,
    messageForDistributor,
    vapid
);

Unsubscribe

To unsubscribe, simply call unregister. Set the instance you want to unsubscribed to if you used one during registration.

It removes the distributor if this is the last instance to unregister.

Regular re-registration

To ensure the distributor is still installed, and the application is correctly registered, it is recommended to regularly re-register to the distributor.

For this, from time to time, like every time the application starts, you can control if the distributor is still installed with getAckDistributor, then call register.

If the previous distributor is uninstalled, you can inform the user and/or fallback to the default one again, with tryUseCurrentOrDefaultDistributor.