Adobe Creative SDK


Android: Migration guide, 0.5.3 to 0.7.329

Migrating to the Creative SDK version 0.7.329 for Android is intended to be quite straightforward. However, there are a few changes you should be aware of when upgrading the SDK.


Asset Browser UI and API split

To help keep the size of the SDK down when you integrate, the former monolithic Asset Browser component ( has been split into Asset UX and Asset Core directories.

When integrating the SDK for accessing Creative Cloud assets, you can choose either of the following two options.

Asset Browser UI

The Asset UX directory contains the Asset Browser UI component. If your integration uses this component, be sure to update your Gradle dependencies to include:

Headless APIs

The Asset Core directory contains the headless APIs for working with Creative Cloud assets. If your integration implements a custom solution for interacting with Creative Cloud assets (i.e. without the Asset Browser UI component), be sure to update your Gradle depencencies to include:

Handling exceptions for AdobeUXAssetBrowser.popupFileBrowser()

Previously, it was possible to call AdobeUXAssetBrowser without a try/catch:

AdobeUXAssetBrowser assetBrowser = AdobeUXAssetBrowser.getSharedInstance();

assetBrowser.popupFileBrowser(this, DEFAULT_SIGN_IN_REQUEST_CODE, browserConfiguration);

Starting in 0.7.329, you will need to handle an AdobeCSDKException in a try/catch statement:

AdobeUXAssetBrowser assetBrowser = AdobeUXAssetBrowser.getSharedInstance();

try {
    assetBrowser.popupFileBrowser(this, DEFAULT_SIGN_IN_REQUEST_CODE);
catch (AdobeCSDKException e) {
    Log.e(MainActivity.class.getSimpleName(), e.getMessage());

Be sure to handle the exception or you will get compile time errors. Android Studio should be helpful in pointing out if you have an unhandled exception.

Was this article helpful?
1 out of 1 found this helpful


Powered by Zendesk