To version 0.21.x
One of the goals of this release was to get rid of singletons both
EffectPlayer. Now you can create multiple
instances of the classes (however, resources aren't shared yet).
BanubaSdkManager.destroyInstancewere removed. Instead intialize SDK with call to
BanubaSdkManager.initializeand create an instanse of
effectsResourcesPathsargument was removed from BanubaSdkManager construction. Use second argument of
Whenever you need
BanubaSdkManager, just create a class field to access it.
EffectPlayeras an argument in constructor.
MainActivityas an example.
instanceproperty was removed in
BanubaSdkManager. Instead intialize SDK with call to
BanubaSdkManager.initialize, next create and hold a reference to
BanubaSdkManagerin a view controller or an application.
outputServiceare optional now (to reflect the state of
BNBEffectPlayerisn't created). Correct nullabity access to these properties.
Pass a reference to
ViewControlleras an example.
To version 0.27.x
We've made BanubaSdk.framework (written in Swift) callable from Objective-C just adding
attribute to each public function and making classes extend from
NSObject. In most cases you
need nothing to do with your code, but good to mention this change.