There are issues with this pod for customers who use use_frameworks! to build their apps because of a transitive dependency from Adobe that has a static library instead of a framework. This has caused customers errors such as "target has transitive dependencies that include statically linked binaries” when installing the pod. This is largely and issue for customers implementing with Swift apps which prefers dynamic libraries, and the current Segment Adobe Analytics SDK requires the entire environment n which it is included (ie. all pods) to be static. For some customers their other pods are built as dynamic libraries so usage of our statically linked library is disallowed and causes build errors.
To fix this:
Add s.static-framework = true
Move the imports of ADBMediaHeartbeat.h and ADBMediaHeartbeatConfig.hinto the .m file and declare the imports using a forward declaration with @class in the header fi.e.
Fix unit tests
Goal: Run pod spec lint without any errors and without --use-libraries flag without errors.
There are issues with this pod for customers who use
use_frameworks!to build their apps because of a transitive dependency from Adobe that has a static library instead of a framework. This has caused customers errors such as "target has transitive dependencies that include statically linked binaries” when installing the pod. This is largely and issue for customers implementing with Swift apps which prefers dynamic libraries, and the current Segment Adobe Analytics SDK requires the entire environment n which it is included (ie. all pods) to be static. For some customers their other pods are built as dynamic libraries so usage of our statically linked library is disallowed and causes build errors.To fix this:
s.static-framework = trueADBMediaHeartbeat.handADBMediaHeartbeatConfig.hinto the.mfile and declare the imports using a forward declaration with@classin the header fi.e.Goal: Run
pod spec lintwithout any errors and without--use-librariesflag without errors.