Publish/Subscribe API for PubNub Android SDK

The foundation of the PubNub service is the ability to send a message and have it delivered anywhere in less than 100ms. Send a message to just one other person, or broadcast to thousands of subscribers at once.

For higher-level conceptual details on publishing and subscribing, refer to Connection Management and to Publish Messages.

Publish​

The publish() function is used to send a message to all subscribers of a channel. To publish a message you must first specify a valid publishKey at initialization. A successfully published message is replicated across the PubNub Real-Time Network and sent simultaneously to all subscribed clients on a channel.

Messages in transit can be secured from potential eavesdroppers with SSL/TLS by setting ssl to true during initialization.

Publish Anytime​

It's not required to be subscribed to a channel in order to publish to that channel.

Message Data​

The message argument can contain any JSON serializable data, including: Objects, Arrays, Ints and Strings. data should not contain special Android classes or functions as these will not serialize. String content can include any single-byte or multi-byte UTF-8 character.

Don't JSON serialize

It is important to note that you should not JSON serialize when sending signals/messages via PUBNUB. Why? Because the serialization is done for you automatically. Instead just pass the full object as the message payload. PubNub takes care of everything for you.

Message Size​

The maximum number of characters per message is 32 KiB by default. The maximum message size is based on the final escaped character count, including the channel name. An ideal message size is under 1800 bytes which allows a message to be compressed and sent using single IP datagram (1.5 KiB) providing optimal network performance.

If the message you publish exceeds the configured size, you will receive the following message:

Message Too Large Error​
["PUBLISHED",[0,"Message Too Large","13524237335750949"]]

For further details, check Calculating Message Payload Size Before Publish.

Message Publish Rate​

Messages can be published as fast as bandwidth conditions will allow. There is a soft limit based on max throughput since messages will be discarded if the subscriber can't keep pace with the publisher.

For example, if 200 messages are published simultaneously before a subscriber has had a chance to receive any messages, the subscriber may not receive the first 100 messages because the message queue has a limit of only 100 messages stored in memory.

Publishing to Multiple Channels​

It is not possible to publish a message to multiple channels simultaneously. The message must be published to one channel at a time.

Publishing Messages Reliably​

There are some best practices to ensure messages are delivered when publishing to a channel:

  • Publish to any given channel in a serial manner (not concurrently).

  • Check that the return code is success (for example, [1,"Sent","136074940..."])

  • Publish the next message only after receiving a success return code.

  • If a failure code is returned ([0,"blah","<timetoken>"]), retry the publish.

  • Avoid exceeding the in-memory queue's capacity of 100 messages. An overflow situation (aka missed messages) can occur if slow subscribers fail to keep up with the publish pace in a given period of time.

  • Throttle publish bursts in accordance with your app's latency needs, for example, Publish no faster than 5 msgs per second to any one channel.

Method(s)​

To Publish a message you can use the following method(s) in the Android SDK:

this.pubnub.publish()
    .message(Object)
    .channel(String)
    .shouldStore(Boolean)
    .meta(Object)
    .queryParam(HashMap)
    .usePOST(Boolean)
    .ttl(Integer);
ParameterTypeRequiredDefaultDescription
messageObjectYesThe payload.
channelStringYesDestination of the message.
shouldStoreBooleanOptionalaccount defaultStore in history.
If shouldStore is not specified, then the history configuration on the key is used.
metaObjectOptionalNot setMeta data object which can be used with the filtering ability.
queryParamHashMap<string,string>OptionalNot setOne or more query parameters to be passed to the server, for analytics purposes. Overridden in case of conflicts with reserved PubNub parameters, such as uuid or instance_id. Accessible from your PubNub Dashboard, and never returned in server responses.
usePOSTBooleanOptionalfalseUse POST to publish.
ttlIntegerOptionalSet a per message time to live in Message Persistence.
  1. If shouldStore = true, and ttl = 0, the message is stored with no expiry time.
  2. If shouldStore = true and ttl = X (X is an Integer value), the message is stored with an expiry time of X hours.
  3. If shouldStore = false, the ttl parameter is ignored.
  4. If ttl is not specified, then expiration of the message defaults back to the expiry value for the key.
syncCommandOptionalBlock the thread, exception thrown if something goes wrong.
asyncPNCallbackOptionalPNCallback of type PNPublishResult

Basic Usage​

Publish a message to a channel​

JsonObject position = new JsonObject();
position.addProperty("lat", 32L);
position.addProperty("lng", 32L);

System.out.println("before pub: " + position);
pubnub.publish()
    .message(position)
    .channel("my_channel")
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            // handle publish result, status always present, result if successful
            // status.isError() to see if error happened
            if(!status.isError()) {
                System.out.println("pub timetoken: " + result.getTimetoken());
show all 19 lines
Subscribe to the channel

Before running the above publish example, either using the Debug Console or in a separate script running in a separate terminal window, subscribe to the same channel that is being published to.

Returns​

The publish() operation returns a PNPublishResult which contains the following operations:

MethodTypeDescription
getTimetoken()LongReturns a long representation of the timetoken when the message was published.

Other Examples​

Publish with metadata​

pubnub.publish()
    .message(Arrays.asList("hello", "there"))
    .channel("suchChannel")
    .shouldStore(true)
    .meta(<Object>) // optional meta data object which can be used with the filtering ability.
    .usePOST(true)
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            // handle publish result, status always present, result if successful
            // status.isError to see if error happened
        }
    });

Publishing JsonObject (Google GSON)​

JsonObject position = new JsonObject();
position.addProperty("lat", 32L);
position.addProperty("lng", 32L);

System.out.println("before pub: " + position);
pubnub.publish()
    .message(position)
    .channel("my_channel")
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            // handle publish result, status always present, result if successful
            // status.isError() to see if error happened
            if(!status.isError()) {
                System.out.println("pub timetoken: " + result.getTimetoken());
show all 19 lines

Publishing JsonArray (Google GSON)​

JsonArray position = new JsonArray();
position.add(32L);

System.out.println("before pub: " + position);
pubnub.publish()
    .message(position)
    .channel("my_channel")
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            //  handle publish result, status always present, result if successful
            //  status.isError to see if error happened
            if(!status.isError()) {
                System.out.println("pub timetoken: " + result.getTimetoken());
            }
show all 18 lines

Publishing JSONObject (org.json)​

JSONObject position = new JSONObject();
position.put("lat", 32L);
position.put("lng", 32L);

System.out.println("before pub: " + position);
pubnub.publish()
    .message(toMap(position))
    .channel("my_channel")
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            // handle publish result, status always present, result if successful
            // status.isError to see if error happened
            if(!status.isError()) {
                System.out.println("pub timetoken: " + result.getTimetoken());
show all 19 lines
Helper Functions​
public static Map<String, Object> toMap(JSONObject object) throws JSONException {
    Map<String, Object> map = new HashMap<>();

    Iterator<String> keysItr = object.keys();
    while(keysItr.hasNext()) {
        String key = keysItr.next();
        Object value = object.get(key);

        if(value instanceof JSONArray) {
            value = toList((JSONArray) value);
        }

        else if(value instanceof JSONObject) {
            value = toMap((JSONObject) value);
        }
show all 35 lines

Publishing JSONArray (org.json)​

JSONArray position = new JSONArray();
position.put(32L);

System.out.println("before pub: " + position);
pubnub.publish()
    .message(toList(position))
    .channel("my_channel")
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            //  handle publish result, status always present, result if successful
            //  status.isError to see if error happened
            if(!status.isError()) {
                System.out.println("pub timetoken: " + result.getTimetoken());
            }
show all 18 lines
Helper Functions​
public static List<Object> toList(JSONArray array) throws JSONException {
    List<Object> list = new ArrayList<>();
    for(int i = 0; i < array.length(); i++) {
        Object value = array.get(i);
        if(value instanceof JSONArray) {
            value = toList((JSONArray) value);
        }

        else if(value instanceof JSONObject) {
            value = toMap((JSONObject) value);
        }
        list.add(value);
    }
    return list;
}

Store the published message for 10 hours​

PNPublishResult result = pubnub.publish()
                                .channel("coolChannel")
                                .message("test")
                                .shouldStore(true)
                                .ttl(10)
                                .sync();

Fire​

The fire endpoint allows the client to send a message to Functions Event Handlers. These messages will go directly to any Event Handlers registered on the channel that you fire to and will trigger their execution. The content of the fired request will be available for processing within the Event Handler. The message sent via fire() isn't replicated, and so won't be received by any subscribers to the channel. The message is also not stored in history.

Method(s)​

To Fire a message you can use the following method(s) in the Android SDK:

this.pubnub.fire()
    .message(Object)
    .channel(String)
    .meta(Object)
    .usePOST(Boolean);
ParameterTypeRequiredDefaultDescription
messageObjectYesThe payload.
channelStringYesDestination of the message.
metaObjectOptionalNot setMeta data object which can be used with the filtering ability.
usePOSTBooleanOptionalfalseUse POST to publish.
syncCommandOptionalBlock the thread, exception thrown if something goes wrong.
asyncPNCallbackOptionalPNCallback of type PNPublishResult

Basic Usage​

Fire a message to a channel​

pubnub.fire()
    .message(Arrays.asList("hello", "there"))
    .channel("my_channel")
    .usePOST(true)
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult result, PNStatus status) {
            if (status.isError()) {
                // something bad happened.
                System.out.println("error happened while publishing: " + status.toString());
            } else {
                System.out.println("publish worked! timetoken: " + result.getTimetoken());
            }
        }
    });

Signal​

The signal() function is used to send a signal to all subscribers of a channel.

By default, signals are limited to a message payload size of 64 bytes. This limit applies only to the payload, and not to the URI or headers. If you require a larger payload size, please contact support.

Method(s)​

To Signal a message you can use the following method(s) in the Android SDK:

this.pubnub.signal()
    .message(Object)
    .channel(String);
ParameterTypeRequiredDescription
messageObjectYesThe payload which will be serialized and sent.
channelStringYesThe channel which the signal will be sent to.
syncPNPublishResultOptionalExecutes the call. Blocks the thread, exception is thrown if something goes wrong.
asyncPNCallback<PNPublishResult>OptionalExecutes the call asynchronously.

Basic Usage​

Signal a message to a channel​

pubnub.signal()
    .message("Hello everyone!")
    .channel("bar")
    .async(new PNCallback<PNPublishResult>() {
        @Override
        public void onResponse(PNPublishResult pnPublishResult, PNStatus pnStatus) {
            if (pnStatus.isError()) {
                Long timetoken = pnPublishResult.getTimetoken(); // signal message timetoken
            } else {
                pnStatus.getErrorData().getThrowable().printStackTrace();
            }
        }
    });

Response​

The signal() operation returns a PNPublishResult object which contains the following operations:

MethodTypeDescription
getTimetoken()LongReturns a long representation of the timetoken when the signal was published.

Subscribe​

The subscribe function creates an open TCP socket to PubNub and begins listening for messages and events on a specified entity or set of entities. To subscribe successfully, you must configure the appropriate subscribeKey at initialization.

Entities are first-class citizens that provide access to their encapsulated APIs. You can subscribe using the PubNub client object or directly on a specific entity:

A newly subscribed client receives messages after the subscribe() call completes. You can configure retryConfiguration to automatically attempt to reconnect if a client gets disconnected.

Subscription scope​

Subscription objects provide an interface to attach listeners for various real-time update types. Your app receives messages and events via those event listeners. Two types of subscriptions are available:

  • Subscription, created from an entity with a scope of only that entity (for example, a particular channel)
  • SubscriptionSet, created from the PubNub client with a global scope (for example, all subscriptions created on a single pubnub object ). A subscription set can have one or more subscriptions.

The event listener is a single point through which your app receives all the messages, signals, and events in the entities you subscribed to. For information on adding event listeners, refer to Event listeners.

Create a subscription​

Managing subscription lifecycle

The Subscription object implements the AutoCloseable interface to help you release resources by unsubscribing and removing all listeners. Always call Subscription.close() when you no longer need this Subscription.

An entity-level Subscription allows you to receive messages and events for only that entity for which it was created. Using multiple entity-level Subscriptions is useful for handling various message/event types differently in each channel.

// Entity-based, local-scoped

// Specify the channel for subscription
val myChannel = pubnub.channel("channelName")

// Create subscription options, if any
val options = SubscriptionOptions.receivePresenceEvents()

// Return a Subscription object that is used to establish the subscription
val subscription = myChannel.subscription(options)

// Activate the subscription to start receiving events
subscription.subscribe()
ParameterTypeRequiredDescription
optionsSubscriptionOptionsNoSubscription behavior configuration. Use null for no specific options.

Create a subscription set​

Managing subscription lifecycle

The SubscriptionSet object implements the AutoCloseable interface to help you release resources by unsubscribing and removing all listeners. Always call SubscriptionSet.close() when you no longer need this SubscriptionSet.

A client-level SubscriptionSet allows you to receive messages and events for all entities in the set. A single SubscriptionSet is useful for similarly handling various message/event types in each channel.

// client-based, general-scoped

fun subscriptionSetOf(
        channels: Set<String> = emptySet(),
        channelGroups: Set<String> = emptySet(),
        options: SubscriptionOptions = EmptyOptions
    ): SubscriptionSet
ParameterTypeRequiredDescription
 → channelsSet<String>NoSet of channel names to subscribe to. Use an empty set for no channels.
 → channelGroupsSet<String>NoSet of channel group names to subscribe to. Use an empty set for no channel groups.
 → optionsSubscriptionOptionsNoAdditional subscription configuration to define the subscription behavior. If you don't set any options, EmptyOptions is used by default.
Add/remove sets

You can add and remove subscription sets to create new sets. Refer to the Other examples section for more information.

SubscriptionOptions​

SubscriptionOptions is a class designed to configure subscription behaviors with optional modifiers. When no specific options are required, EmptyOptions is set by default.

The class includes:

OptionDescription
receivePresenceEvents()Enables receiving presence events for the subscription. It's not required and should be included only when presence information is needed.
filter(predicate: (PNEvent) -> Boolean)Allows for custom filtering of events delivered to the subscription based on the provided predicate. Useful for event-specific handling.

Method(s)​

Subscription and SubscriptionSet use the same methods to subscribe:

Subscribe​

To subscribe, you can use the following method:

// For subscription
subscription.subscribe()
// For subscription set
subscriptionSet.subscribe()
Basic usage​
// Step 1: Create a subscription set
val subscriptionSet = pubnub.subscriptionSetOf(
    // Specify channels with default options
    channels = setOf("my_channel", "other_channel"),
)

// Step 2: Subscribe using the subscription set
subscriptionSet.subscribe()
Other examples​
Create a subscription set from 2 individual subscriptions​
// Create subscriptions
val subscription1 = pubnub.channel("channelName").subscription()
val subscription2 = pubnub.channelGroup("channelGroup").subscription()

// Combine into a subscription set
val subscriptionSet = subscription1 + subscription2
Returns​

The subscribe() method doesn't have a return value.

Subscribe with timetoken​

Impact on other subscriptions

Subscribing with a timetoken affects all other subscriptions because it overwrites the timetoken in the single PubNub server connection in the SDK. However, those other subscriptions will not deliver messages older than ones that were already delivered - after receiving an event, a subscription only gets future events, ignoring those before or at the time of the last event received.

To subscribe to real-time updates from a given timetoken, use the following method:

subscriptionSet.subscribe(SubscriptionCursor(timetoken = yourTimeToken))
ParameterTypeRequiredDescription
cursorSubscriptionCursorYesCursor from which to return any available cached messages. SubscriptionCursor would typically include a timetoken (long integer) representing the point in time from which to receive updates.
Basic usage​
// Define the channels to subscribe to
val channels = setOf("my_channel", "other_channel")

// Create a subscription set with specified channels and subscription options
val subscriptionSet = pubnub.subscriptionSetOf(channels, options)

// Define the timetoken for where the subscription should start
val yourTimeToken = 100000000000L // Directly using Long type

// Subscribe to the created SubscriptionSet with the desired timetoken
subscriptionSet.subscribe(SubscriptionCursor(timetoken = yourTimeToken))
Returns​

The method for subscribing with a timetoken doesn't have a return value.

Entities​

Entities are subscribable objects for which you can receive real-time updates (messages, events, etc).

Create channels​

This method returns one local Channel entity.

pubnub.channel(name: String): Channel
ParameterTypeRequiredDescription
nameStringYesThe name of a single channel to create a channel entity for.

Basic usage​

val singleChannel = pubnub.channel("myChannel")

Create channel groups​

This method returns one local ChannelGroup entity.

pubnub.channelGroup(name: String): ChannelGroup
ParameterTypeRequiredDescription
nameStringYesThe name of a single channel group to create an entity for.

Basic usage​

val myChannelGroup = pubnub.channelGroup("myGroup")

Create channel metadata​

This method returns one local ChannelMetadata entity.

pubnub.channelMetadata(id: String): ChannelMetadata
ParameterTypeRequiredDescription
idStringYesThe String identifier for a single channel metadata object to create a subscription of.

Basic usage​

val metadata = pubnub.channelMetadata("myChannel")

Create user metadata​

This method returns one local UserMetadata entity.

pubnub.userMetadata(userId: String): UserMetadata
ParameterTypeRequiredDescription
userIdStringYesThe String identifier for a single user metadata object to manage user information.

Basic usage​

val userMetadata = pubnub.userMetadata("userId1")

Event listeners​

Messages and events are received in your app using a listener. This listener allows a single point to receive all messages, signals, and events.

You can attach listeners to the instances of Subscription, SubscriptionSet, and, in the case of the connection status, the PubNub client.

Add listeners​

You can add listeners for various types of updates related to your subscription. You can implement listeners for general updates (that handle multiple event types at once) or choose listeners dedicated to specific event types such as Message or File.

Handle multiple event types​

Method(s)​
fun addListener(listener: EventListener)
Basic usage​
// Create a subscription to a specific channel
val subscription = pubnub.channel("my_channel").subscription()

// Add a listener to the subscription for handling various event types
subscription.addListener(object : EventListener {
    override fun message(pubnub: PubNub, message: PNMessageResult) {
        // Log or process message
        println("Message: ${message.message}")
    }
    
    override fun signal(pubnub: PubNub, signal: PNSignalResult) {
        // Handle signals
        println("Signal: ${signal.message}")
    }
show all 41 lines

Handle one event type​

Method(s)​

You can also directly register listeners for specific event types on the subscription object by assigning lambda expressions. This method allows you to handle events such as messages, signals, message actions, files, objects, and presence.

Using this method, you cannot have multiple listeners attached to the same event type. Assigning a new listener with this method overwrites the previous one.

Basic usage​
subscription.onMessage = { message ->
    /* Handle message */
}

subscription.onSignal = { signal ->
    /* Handle signal */
}

subscription.onMessageAction = { messageAction ->
    /* Handle message action */
}

subscription.onFile = { file ->
    /* Handle file event */
}
show all 23 lines
Remove event listener​

To remove the listener for a specific event, assign null to it.

subscription.onMessage = null

Add connection status listener​

Use the StatusListener interface with your PubNub instance to add a listener dedicated to connection status updates.

Client scope

This listener is only available on the PubNub object.

Method(s)​

pubnub.addListener(object : StatusListener() {
    override fun status(pubnub: PubNub, status: PNStatus) {
        // Handle connection status updates
        println("Connection Status: ${status.category}")
    }
})

Basic usage​

// Adding the status listener to the PubNub client
pubnub.addListener(object : StatusListener() {
    override fun status(pubnub: PubNub, status: PNStatus) {
        // This block is executed asynchronously for each status update
        println("Connection Status: ${status.category}")
    }
})

Returns​

This method returns the subscription status.

When you initialized your PubNub client with enableEventEngine set to true (default option), the SDK will emit various statuses depending on your client network connection.

If you use the deprecated methods for subscribing and had enableEventEngine set to false, the status list the SDK emits is different.

To help you adjust your app code, see the Status Events for Subscribe for the exact mapping between the current and deprecated Kotlin SDK statuses.

For more generic information, head to SDK Connection Lifecycle.

Unsubscribe​

Stop receiving real-time updates from a Subscription or a SubscriptionSet.

Method(s)​

// For subscription
subscription.unsubscribe()
// For subscription set
subscriptionSet.unsubscribe()

Basic Usage​

// Subscribe to a channel
subscription.subscribe()

// Unsubscribe from that channel
subscription.unsubscribe()

Returns​

None

Unsubscribe All​

Stop receiving real-time updates from all listeners and remove the entities associated with them.

Client scope

This method is only available on the PubNub object.

Method(s)​

pubnub.unsubscribeAll()

Basic Usage​

// Subscribe to channels
pubnub.subscribe(channels = setOf("my_channel", "other_channel"))

// Subscribe to a channel group
pubnub.subscribe(channelGroups = setOf("my_channel_group"))

// Later, when you want to unsubscribe from all subscriptions
pubnub.unsubscribeAll()

Returns​

None

Subscribe (deprecated)​

Deprecated

This method is deprecated. Use Subscribe instead.

This function causes the client to create an open TCP socket to the PubNub Real-Time Network and begin listening for messages on a specified channel. To subscribe to a channel the client must send the appropriate subscribeKey at initialization.

By default a newly subscribed client will only receive messages published to the channel after the subscribe() call completes. If a client gets disconnected from a channel, it can automatically attempt to reconnect to that channel and retrieve any available messages that were missed during that period. This can be achieved by setting setReconnectionPolicy to PNReconnectionPolicy.LINEAR, when initializing the client.

Unsubscribing from all channels

Unsubscribing from all channels, and then subscribing to a new channel Y is not the same as subscribing to channel Y and then unsubscribing from the previously-subscribed channel(s). Unsubscribing from all channels resets the last-received timetoken and thus, there could be some gaps in the subscription that may lead to message loss.

Method(s)​

To Subscribe to a channel you can use the following method(s) in the Android SDK:

pubnub.subscribe()
    .channels(Array)
    .channelGroups(Arrays)
    .withTimetoken(Long)
    .withPresence()
    .execute();
ParameterTypeRequiredDescription
channelsArrayOptionalSubscribe to channels, Either channel or channelGroup is required
channelGroupsArrayOptionalSubscribe to channel groups, Either channel or channelGroup is required
withTimetokenLongOptionalPass a timetoken
withPresence()CommandOptionalAlso subscribe to related presence information
execute()CommandYesCommand that will execute subscribe.

Basic Usage​

Subscribe to a channel:

pubnub.subscribe()
    .channels(Arrays.asList("my_channel")) // subscribe to channels
    .execute();
Event listeners

The response of the call is handled by adding a Listener. Please see the Listeners section for more details. Listeners should be added before calling the method.

Returns​

PNMessageResult

PNMessageResult is returned in the Listeners.

The subscribe() operation returns a PNStatus which contains the following operations:

MethodTypeDescription
getCategory()Enum of type PNStatusCategory.Details of PNStatusCategory are here
isError()BooleanIs true in case of an error.

The subscribe() operation returns a PNMessageResult for messages which contains the following operations:

MethodTypeDescription
getMessage()JsonElementThe message sent on the channel.
getSubscription()StringThe channel group or wildcard subscription match (if exists).
getChannel()StringThe channel for which the message belongs.
getTimetoken()LongTimetoken for the message.
getUserMetadata()ObjectUser metadata.

The subscribe() operation returns a PNPresenceEventResult from presence which contains the following operations:

MethodTypeDescription
getEvent()StringEvents like join, leave, timeout, state-change, interval.
getUuid()StringUUID for the event.
getTimestamp()LongTimestamp for the event.
getOccupancy()IntCurrent occupancy.
getState()JsonElementState of the UUID.
getSubscription()StringThe channel group or wildcard subscription match (if exists).
getChannel()StringThe channel for which the message belongs.
getTimetoken()LongTimetoken of the message.
getUserMetadata()ObjectUser metadata.

The subscribe() operation returns a PNSignalResult for signals which contains the following operations:

MethodTypeDescription
getMessage()JsonElementThe signal sent on the channel.
getSubscription()StringThe channel group or wildcard subscription match (if exists).
getChannel()StringThe channel for which the signal belongs.
getTimetoken()LongTimetoken for the signal.
getUserMetadata()ObjectUser metadata.

Other Examples​

Basic subscribe with logging​
PNConfiguration pnConfiguration = new PNConfiguration();
// subscribeKey from admin panel
pnConfiguration.setSubscribeKey("my_subkey"); // required
// publishKey from admin panel (only required if publishing)
pnConfiguration.setPublishKey("my_pubkey");
pnConfiguration.setLogVerbosity(PNLogVerbosity.BODY);
PubNub pubnub = new PubNub(pnConfiguration);

pubnub.subscribe()
    .channels(Arrays.asList("my_channel")) // subscribe to channels information
    .execute();
Subscribing to multiple channels​

It's possible to subscribe to more than one channel using the Multiplexing feature. The example shows how to do that using an array to specify the channel names.

Alternative subscription methods

You can also use Wildcard Subscribe and Channel Groups to subscribe to multiple channels at a time. To use these features, the Stream Controller add-on must be enabled on your keyset in the Admin Portal.

pubnub.subscribe()
    .channels(Arrays.asList("my_channel1","my_channel2" )) // subscribe to channels information
    .execute();
Subscribing to a Presence channel​
Requires Message Persistence

This method requires that Message Persistence is enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.

For any given channel there is an associated Presence channel. You can subscribe directly to the channel by appending -pnpres to the channel name. For example the channel named my_channel would have the presence channel named my_channel-pnpres. Presence data can be observed inside the SubscribeCallback#message(PubNub, PNMessageResult) callback.

pubnub.subscribe()
    .channels(Arrays.asList("my_channel")) // subscribe to channels
    .withPresence() // also subscribe to related presence information
    .execute();
Sample Responses​
Join Event​
if (presence.getEvent().equals("join")) {
    presence.getUuid(); // 175c2c67-b2a9-470d-8f4b-1db94f90e39e
    presence.getTimestamp(); // 1345546797
    presence.getOccupancy(); // 2
}
Leave Event​
if (presence.getEvent().equals("leave")) {
    presence.getUuid(); // 175c2c67-b2a9-470d-8f4b-1db94f90e39e
    presence.getTimestamp(); // 1345546797
    presence.getOccupancy(); // 2
}
Timeout Event​
if (presence.getEvent().equals("timeout")) {
    presence.getUuid(); // 175c2c67-b2a9-470d-8f4b-1db94f90e39e
    presence.getTimestamp(); // 1345546797
    presence.getOccupancy(); // 2
}
Custom Presence Event (State Change)​
{
    "action": "state-change",
    "uuid": "76c2c571-9a2b-d074-b4f8-e93e09f49bd",
    "timestamp": 1345549797,
    "data": {
        "isTyping": true
    }
}
Interval Event​
if (presence.getEvent().equals("interval")) {
    presence.getUuid(); // 175c2c67-b2a9-470d-8f4b-1db94f90e39e
    presence.getTimestamp(); // 1345546797
    presence.getOccupancy(); // 2
}

When a channel is in interval mode with presence_deltas pnconfig flag enabled, the interval message may also include the following fields which contain an array of changed UUIDs since the last interval message. This settings can be altered in the Admin Portal

  • joined
  • left
  • timedout

For example, this interval message indicates there were 2 new UUIDs that joined and 1 timed out UUID since the last interval:

if (presence.getEvent().equals("interval")) {
    presence.getTimestamp(); // <unix timestamp>
    presence.getOccupancy(); // <# users in channel>
    presence.getJoin(); // ["uuid1", "uuid2"]
    presence.getTimeout(); // ["uuid3"]
}

If the full interval message is greater than 30KB (since the max publish payload is ∼32KB), none of the extra fields will be present. Instead there will be a here_now_refresh boolean field set to true. This indicates to the user that they should do a hereNow request to get the complete list of users present in the channel.

if (presence.getEvent().equals("interval")) {
    presence.getTimestamp(); // <unix timestamp>
    presence.getOccupancy(); // <# users in channel>
    presence.getHereNowRefresh() // true
}
Wildcard subscribe to channels​
Requires Stream Controller add-on

This method requires that the Stream Controller add-on is enabled for your key in the Admin Portal (with Enable Wildcard Subscribe checked). Read the support page on enabling add-on features on your keys.

Wildcard subscribes allow the client to subscribe to multiple channels using wildcard. For example, if you subscribe to a.* you will get all messages for a.b, a.c, a.x. The wildcarded * portion refers to any portion of the channel string name after the dot (.).

pubnub.subscribe()
    .channels(Arrays.asList("foo.*")) // subscribe to channels information
    .execute();
Wildcard grants and revokes

Only one level (a.*) of wildcarding is supported. If you grant on * or a.b.*, the grant will treat * or a.b.* as a single channel named either * or a.b.*. You can also revoke permissions from multiple channels using wildcards but only if you previously granted permissions using the same wildcards. Wildcard revokes, similarly to grants, only work one level deep, like a.*.

Subscribing with State​
Requires Presence add-on

This method requires that the Presence add-on is enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.

Required UUID

Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. If you don't set the UUID, you won't be able to connect to PubNub.

PNConfiguration pnConfiguration = new PNConfiguration();
pnConfiguration.setSubscribeKey("demo");
pnConfiguration.setPublishKey("demo");

class complexData {
    String fieldA;
    int fieldB;
}

PubNub pubnub= new PubNub(pnConfiguration);

pubnub.addListener(new SubscribeCallback() {
    @Override
    public void status(PubNub pubnub, PNStatus status) {
        if (status.getCategory() == PNStatusCategory.PNConnectedCategory){
show all 42 lines
Subscribe to a channel group​
Requires Stream Controller add-on

This method requires that the Stream Controller add-on is enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.

pubnub.subscribe()
    .channels(Arrays.asList("ch1", "ch2")) // subscribe to channels
    .channelGroups(Arrays.asList("cg1", "cg2")) // subscribe to channel groups
    .withTimetoken(1337L) // optional, pass a timetoken
    .withPresence() // also subscribe to related presence information
    .execute();
Subscribe to the presence channel of a channel group​
note
Requires Stream Controller and Presence add-ons

This method requires both the Stream Controller and Presence add-ons are enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.

pubnub.subscribe()
    .channelGroups(Arrays.asList("cg1", "cg2")) // subscribe to channel groups
    .withTimetoken(1337L) // optional, pass a timetoken
    .withPresence() // also subscribe to related presence information
    .execute();

Event Listeners​

You can be notified of connectivity status, message and presence notifications via the listeners.

Listeners should be added before calling the method.

Add Listeners​
pubnub.addListener(new SubscribeCallback() {
    // PubNub status
    @Override
    public void status(PubNub pubnub, PNStatus status) {
        switch (status.getOperation()) {
            // combine unsubscribe and subscribe handling for ease of use
            case PNSubscribeOperation:
            case PNUnsubscribeOperation:
                // Note: subscribe statuses never have traditional errors,
                // just categories to represent different issues or successes
                // that occur as part of subscribe
                switch (status.getCategory()) {
                    case PNConnectedCategory:
                        // No error or issue whatsoever.
                    case PNReconnectedCategory:
show all 129 lines
Remove Listeners​
SubscribeCallback subscribeCallback = new SubscribeCallback() {
    @Override
    public void status(PubNub pubnub, PNStatus status) {

    }

    @Override
    public void message(PubNub pubnub, PNMessageResult message) {

    }

    @Override
    public void presence(PubNub pubnub, PNPresenceEventResult presence) {

    }
show all 52 lines
Handling Disconnects​
SubscribeCallback subscribeCallback = new SubscribeCallback() {
    @Override
    public void status(PubNub pubnub, PNStatus status) {
        if (status.getCategory() == PNStatusCategory.PNUnexpectedDisconnectCategory) {
            // internet got lost, do some magic and call reconnect when ready
            pubnub.reconnect();
        } else if (status.getCategory() == PNStatusCategory.PNTimeoutCategory) {
            // do some magic and call reconnect when ready
            pubnub.reconnect();
        } else {
            log.error(status);
        }
    }

    @Override
show all 26 lines
Listener status events​
CategoryDescription
PNNetworkUpCategoryThe SDK detected that the network is online.
PNNetworkDownCategoryThe SDK announces this when a connection isn't available, or when the SDK isn't able to reach the PubNub Data Stream Network.
PNNetworkIssuesCategoryA subscribe event experienced an exception when running. The SDK isn't able to reach the PubNub Data Stream Network. This may be due to many reasons, such as: the machine or device isn't connected to the internet; the internet connection has been lost; your internet service provider is having trouble; or, perhaps the SDK is behind a proxy.
PNReconnectedCategoryThe SDK was able to reconnect to PubNub.
PNConnectedCategorySDK subscribed with a new mix of channels. This is fired every time the channel or channel group mix changes.
PNAccessDeniedCategoryAccess Manager permission failure.
PNMalformedResponseCategoryJSON parsing crashed.
PNBadRequestCategoryThe server responded with a bad response error because the request is malformed.
PNDecryptionErrorCategoryIf using decryption strategies and the decryption fails.
PNTimeoutCategoryFailure to establish a connection to PubNub due to a timeout.
PNRequestMessageCountExceedCategoryThe SDK announces this error if requestMessageCountThreshold is set, and the number of messages received from PubNub (in-memory cache messages) exceeds the threshold.
PNUnknownCategoryReturned when the subscriber gets a non-200 HTTP response code from the server.

Unsubscribe (deprecated)​

Deprecated

This method is deprecated. Use Unsubscribe instead.

When subscribed to a single channel, this function causes the client to issue a leave from the channel and close any open socket to the PubNub Network. For multiplexed channels, the specified channel(s) will be removed and the socket remains open until there are no more channels remaining in the list.

Unsubscribing from all channels

Unsubscribing from all channels, and then subscribing to a new channel Y is not the same as subscribing to channel Y and then unsubscribing from the previously-subscribed channel(s). Unsubscribing from all channels resets the last-received timetoken and thus, there could be some gaps in the subscription that may lead to message loss.

Method(s)​

To Unsubscribe from a channel you can use the following method(s) in the Android SDK:

pubnub.unsubscribe()
    .channels(Array)
    .channelGroups(Array)
    .execute();
ParameterTypeRequiredDescription
channelsArrayOptionalUnsubscribe to channels, Either channel or channelGroup is required
channelGroupsArrayOptionalUnsubscribe to channel groups, Either channel or channelGroup is required
execute()CommandYesCommand that will execute unsubscribe.

Basic Usage​

Unsubscribe from a channel:

pubnub.unsubscribe()
    .channels(Arrays.asList("my_channel"))
    .execute();
Event listeners

The response of the call is handled by adding a Listener. Please see the Listeners section for more details. Listeners should be added before calling the method.

Response​

The output below demonstrates the response to a successful call:

@Override
public void presence(PubNub pubnub, PNPresenceEventResult presence) {
    if (presence.getEvent().equals("leave")) {
        presence.getTimestamp(); // 1345546797
        presence.getOccupancy(); // 2
        presence.getUuid(); // left_uuid
    }
}

Other Examples​

Unsubscribing from multiple channels​
Requires Stream Controller add-on

This method requires that the Stream Controller add-on is enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.

pubnub.unsubscribe()
    .channels(Arrays.asList("ch1", "ch2", "ch3"))
    .channelGroups(Arrays.asList("cg1", "cg2", "cg3"))
    .execute();
Example Response​
@Override
public void presence(PubNub pubnub, PNPresenceEventResult presence) {
    if (presence.getEvent().equals("leave")) {
        presence.getTimestamp(); // 1345546797
        presence.getOccupancy(); // 2
        presence.getUuid(); // left_uuid
    }
}
Unsubscribe from a channel group​
pubnub.unsubscribe()
    .channelGroups(Arrays.asList("cg1", "cg2", "cg3"))
    .execute();
Example Response​
@Override
public void presence(PubNub pubnub, PNPresenceEventResult presence) {
    if (presence.getEvent().equals("leave")) {
        presence.getTimestamp(); // 1345546797
        presence.getOccupancy(); // 2
        presence.getUuid(); // left_uuid
    }
}

Unsubscribe All (deprecated)​

Deprecated

This method is deprecated. Use Unsubscribe All instead.

Unsubscribe from all channels and all channel groups

Method(s)​

public final void unsubscribeAll()

Basic Usage​

pubnub.unsubscribeAll();

Returns​

None

Last updated on
On this page