Carthage automatically picks the "Release" configuration for an SDK release but still copies all headers into the framework. This results in a binary that doesn't contain the Feedback-Feature but with all Feedback-Headers being present. So it's possible to integrate it in code but the app will crash at runtime when the dev tries to call, e.g. BITHockeyManager.shared().feedbackManager.showFeedbackListView().
I tried various approaches to solve this and came up with the following: the 'Release'-configuration will now build the full-featured SDK, while the 'ReleaseDefault' will build the default configuration. To the sdk users, this change is transparent.
Carthage automatically picks the "Release" configuration for an SDK release but still copies all headers into the framework. This results in a binary that doesn't contain the Feedback-Feature but with all Feedback-Headers being present. So it's possible to integrate it in code but the app will crash at runtime when the dev tries to call, e.g.
BITHockeyManager.shared().feedbackManager.showFeedbackListView().I tried various approaches to solve this and came up with the following: the 'Release'-configuration will now build the full-featured SDK, while the 'ReleaseDefault' will build the default configuration. To the sdk users, this change is transparent.