Adobe Creative SDK


iOS: Migration guide, from 0.14.2160 Static Frameworks to Dynamic Frameworks

Up until version 0.14.2160 of the Creative SDK, the frameworks that comprise these Creative SDK were only available as static frameworks. Beginning with version 0.14.2160 of the Creative SDK, dynamic frameworks are also available. Dynamic frameworks will be the primary framework type moving forward, and the static frameworks will be removed at some point in the future. Developers should migrate from using the static frameworks to the dynamic frameworks as soon as possible.


The Creative SDK's frameworks have always been delivered as static frameworks because of Apple's lack of support for building dynamic frameworks on iOS. This required some effort as static frameworks have never been officially supported either. In reality, the static frameworks delivered as part of the Creative SDK were in fact static libraries and resource bundles wrapped in a framework directory structure (using static frameworks in this manner simplified delivery of the libraries, headers, and resources via a single bundle).

Beginning in Xcode 6 (and iOS8), Apple has been providing support for creating dynamic frameworks on iOS. Moving to dynamic frameworks has the following advantages:

  • As an SDK provider, building dynamic frameworks is an easier proposition than building static frameworks as they are directly supported within Xcode.
  • It is easier for us to include Swift support.
  • Integration by app developers is greatly simplified as the single step of linking the dynamic framework handles setting up both the exeuctable code and resources.

How to migrate from Creative SDK static frameworks to dynamic frameworks

Refer to the following two documents:

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


Powered by Zendesk