SwiftyBeaver is the first pod that MatrixSDK depends upon that includes Swift code. The normal use of cocoapods in this scenario would be to enable use_frameworks! to expose the modulemap for any Swift packages, however building the framework this way a) fails for Catalyst and b) is no longer easily packaged as multiple frameworks are created, one for each pod.
A workaround for use right now appears to be adding SwiftyBeaver as a Swift package dependency alongside MatrixSDK, but this doesn’t sound super sensible going forward.
SwiftyBeaver is the first pod that MatrixSDK depends upon that includes Swift code. The normal use of cocoapods in this scenario would be to enable
use_frameworks!to expose the modulemap for any Swift packages, however building the framework this way a) fails for Catalyst and b) is no longer easily packaged as multiple frameworks are created, one for each pod.A workaround for use right now appears to be adding SwiftyBeaver as a Swift package dependency alongside MatrixSDK, but this doesn’t sound super sensible going forward.