Versions

This is the developer guide for Chat SDK v1. The new Chat SDK v2 for Android is now available and is the recommended version to integrate Chat into your mobile app.

The Chat SDK uses versioning to ensure that changes to the SDK don't break existing applications without notice. When we add new features or deprecate old features, we do so in the 'Future' version of the SDK so that applications developed in the 'Current' version are unaffected.

Version history

Version Status
1.4.6 Patch release
1.4.5 Patch release
1.4.4 Patch release
1.4.3 Patch release
1.4.2 Patch release
1.4.1 Patch release
1.4.0 SDK version 1.4.0 release
1.3.7.1 Patch release
1.3.6.1 Patch release
1.3.5.1 Patch release
1.3.4.1 Patch release
1.3.3.1 Patch release
1.3.2.1 Patch release
1.3.1.1 Patch release
1.3.0.1 SDK version 1.3.0.1 release
1.2.3.1 Patch release
1.2.2.1 Patch release
1.2.1.1 Patch release
1.2.0.1 SDK version 1.2.0.1 release
1.1.1 Patch release
1.1.0 SDK version 1.1.0 release
1.0.1 Patch release
1.0.0 SDK version 1.0.0 release
0.9.2 Beta
0.9.1 Beta
0.9.0 Beta

Migrating to 1.2.0.1 from 1.1.0 (and older)

Storage permissions

In previous versions, the permission READ_EXTERNAL_STORAGE was needed for attachments. Beginning with version 1.2.0.1, storage permissions are no longer needed. If you're using Gradle to build your project, make sure the applicationId is provided in the module specific configuration file. For more information about placeholder support, see the Android tools documentation. For a project without Gradle support, add the following to the AndroidManifest.xml. Make sure that to replace applicationId with the actual package name of your application.

<provider
  android:name="com.zendesk.belvedere.BelvedereFileProvider"
  android:authorities="<applicationId>.belvedere.attachments"
  android:exported="false"
  android:grantUriPermissions="true">
  <meta-data
    android:name="android.support.FILE_PROVIDER_PATHS"
    android:resource="@xml/belvedere_attachment_storage" />
</provider>
Configuring the attachments provider

Because defining a unique FileProvider authority is no longer required since version 1.2.0.1, you can remove provider_authorities.xml altogether.

Older versions of Chat SDK

To configure attachments properly, create provider_authorities.xml file in your res/values directory like in the example below. Replace the com.zopim.sample.fileprovider with your application package name followed by .fileprovider.

<resources>
    <!--Specify your application's package name followed by .fileprovider to guarantee unique file provider authority-->
    <string name="file_provider_authority">com.zopim.sample.fileprovider</string>
</resources>

For more details, see our sample project with SDK v1.0.1. Learn more about FileProvider in the Android developer docs.

Important: Don't forget to set this before your release or your app might experience installation conflicts.