Closed smawpaw closed 3 years ago
Hi @smawpaw,
Thanks for filing this issue and linking it to the open Cocoapods issue + workaround. It looks like this is a general issue with Pods that have a setup similar to ours. In addition to the workaround linked, you can also explicitly sign each bundle under the Pods
project to allow you to run on Mac Catalyst.
In the past, we haven't code signed our SDK because it wasn't necessary on iOS, and Cocoapods/etc would handle it automatically. However, it appears code signing is handled differently for Mac Catalyst and this issue stems from the same place as the one here. We are currently investigating in regards to signing our SDK for distribution. Let us know if you have any further thoughts.
Thank you!
Updating this thread here - The Mac Catalyst signing issues in this Cocoapods thread are separate from the ones in the related SPM thread (which has been fixed in Xcode 12.5).
Right now the best thing to do if you experience this issue is to follow the workaround provided in the original post above. This should be sufficient until Cocoapods can handle the generic root cause that this issue stems from.
Since there are no action items on our end, I am closing out this thread. If there are any concerns or if the workaround above isn't sufficient, feel free to comment on / reopen. Thank you!
Report
Describe your environment.
What did you do?
What did you expect to happen?
What happened instead?
Signing for "Appboy-iOS-SDK-Appboy" requires a development team. Select a development team in the Signing and Capabilities editor.
Steps to reproduce
Workaround