Closed SunnyGit closed 1 year ago
I'm currently working on trying to reproduce this (updating a second machine to Xcode 14, hence the delay). My hunch is that one of our build configurations for the Operator (development/test) app may have leaked into the ApptentiveKit target.
To help with reproducing it, which integration method are you seeing this issue while using?
I haven't been able to reproduce this with either the SwiftPM or sub-project integration methods.
@frankus We are using cocoapods in this case. I see that in podspec we have resource_bundles which is creating two section on pods target.
pod 'ApptentiveKit'
I've done some more investigation, and this seems to be a more widespread issue with Xcode 14 and/or CocoaPods when building resource bundles (for example, adding the Firebase pod results in the same issue).
The most straightforward resolution is to go to the build settings for the Pods project and set your development team in the Signing section of the build settings.
Depending on how committed you are to CocoaPods, you could also consider integrating using Swift Package Manager. Since it's a first-party Apple solution it may be less likely to break with updates to the development tools.
Having challenge building the app with Xcode 14 and above.
While building the app, we are running into the issue to select development team else we cannot proceed to build.
Signing for "ApptentiveKit-ApptentiveKit" requires a development team. Select a development team in the Signing & Capabilities editor.
Please suggest how to overcome Build automation with the above mentioned issue