The “Cannot Load Bundle” and “Symbol Not Found” errors are typically originating from issues with linking frameworks for your iOS project.
Usercentrics App SDK consists of two modules: UsercentricsCore and UsercentricsUI. UsercentricsUI relies on UsercentricsCore.
The packages are distributed using specific naming conventions. Example naming conventions for each linking type are as follows:
Usercentrics: Usercentrics-2.18.9.xcframework.zip
Usercentrics UI: UsercentricsUI-2.18.9.xcframework.zip
Unity package created for dynamic linking: Usercentrics-2.18.9.unitypackage
Usercentrics: Usercentrics-2.18.9-unity-static.xcframework.zip
UsercentricsUI: UsercentricsUI-2.18.9-unity-static.xcframework.zip
Unity package created for static linking: Usercentrics-2.18.9-static.unitypackage
Manual linking requires the Unity version of the Usercentrics package, as the manual version of UsercentricsUI relies on the Unity version of Usercentrics.
Manual dynamic:
Usercentrics: Usercentrics-2.18.9-unity.xcframework.zip
UsercentricsUI: UsercentricsUI-Manual-Linking-2.18.9.xcframework.zip
Manual static:
Usercentrics: Usercentrics-2.18.9-unity-static.xcframework.zip
UsercentricsUI: UsercentricsUI-Manual-Linking-2.18.9-static.xcframework.zip
Cannot Load Bundle
Typically, this error occurs when the dynamic versions of the SDK packages have been linked statically, or the other way around - when the static versions of the packages have been linked dynamically. Please check the following:
Have you included static or dynamic versions of the SDK packages into your project
If using Cocoapods: ensure the linking in your podfile aligns with your chosen framework files, for example, when working with dynamic frameworks, the podfile needs to be set up dynamically.
If on Unity: double-check which Unity package has been imported (static / dynamic) and adjust your iOS resolver settings accordingly
Symbol Not Found
This error is usually caused by using a non-Unity version of Usercentrics package in combination with the Unity-specific version of UsercentricsUI package. To resolve this error, review the package naming conventions in the Manual linking section above, and replace packages with the correct ones as needed.