The Support library now
builds as an AAR library. You can continue to include the Support library
as a project dependency or you can include the AAR file as a dependency in
your application's build.gradle file.
The Android example applications no longer
require a signing key store when building with the debug configuration.
Voice and video call functionality from the
application has been moved to the
Support library. You
can use and extend this functionality to easily add voice or video call
support to your application.
Global Syncing value indicates when bbmcore is performing reconnect
synchronization with the BlackBerry Infrastructure. Your application
should ensure that the SDK remains active while the GlobalSyncing value is
private data value of a chat to share chat metadata that needs to be
known by all the users endpoints.
The Android example applications and Support library now support sandbox
domains that have user authentication disabled. See the
Download & Configure page for
instructions on how to set up such a domain.
Chat flag has been removed. All chats are always in a protected state.
constructor no longer includes the subject parameter. The subject can
optionally be set using the subject() method.
and RefBy tags are a String value instead
of an Enum. This allows easily setting custom reference
tags. If you have existing code using reference tags ensure you are
comparing tags using equals().
The BBM Enterprise SDK now encrypts all private keys in each example. For
more information see Cloud Key Storage
Deprecated items from R4 have been removed from this
The BBM Enterprise SDK now includes the x86_64 ABI. This inclusion will
let developers use the Android Emulator to run, test, debug your code
without the needs to deploy to a real device. For more information on the
Android Emulator see:
data connection API which allows sharing data in securely over a peer
to peer connection. See the
Transfer example for a guide on using the data connection API to share
Support Library: UI
Widgets The Support Library now includes several reusable UI widgets
as well as other related code and utilities. Refer to the
or RichChat application
for an example of how to integrate this code into your application.
Support Library: Analytics The Support Library
now includes AnalyticsUtil which can be used to gather and report usage
and other information about your application.
GlobalHasNewMessage has been deprecated and will be removed in a future release.
The BBM Enterprise SDK BbmSdkSupport library has been renamed to BBM
Enterprise SDK Support.
Build an application to share files using the BBM Enterprise SDK.
Build an application that allows users to send, view, and edit
announcements in a chat, and view their change history.
Android Jelly Bean API 18 is no longer supported. The
minimum version target is Android KitKat, API 19+.
Multiple Points of Presence The BBM Enterprise SDK
now allows applications to have multiple instances running and connected
at the same time for the same user. Each endpoint will receive messages
and voice and video calls.
Group chats now support having
InvitePolicies. Chat administrators can remove participants or delete
a chat from all users devices. The invite policy can be set to allow
invites only by the administrator.
The change results in a new inheritance chain for ObservableList
and allows developers to use the new StateAware interface for more
than just lists.
The displayName property has been removed from the
class. Previously this value was always empty. This change also resulted
in the removal of the ProfileChange message, and displayName being removed
ChatParticipant list replaces the Participant list. ChatParticipant
is identical to Participant but replaces the conversationUri with a
list replaces the TypingUser list. Typing is identical to TypingUser but
replaces the conversationUri with a chatId.
Build an application with voice and video calling using the BBM Enterprise
Build a shared white board application with the BBM Enterprise SDK.
replaces the Basic Setup example from R3.
You can now control the native logging of the BBM
Use the <meta-data
android:value="android.util.Log.DEBUG"/> manifest flag to
control the native log level and the <meta-data
android:value="android.util.Log.DEBUG"/> flag will redirect
native logging into logcat.
The first release of BBM Enterprise SDK for Android