This issue was basically closed with the comment: "Just use CocoaPods". As far as I know there are some developers out there, who do not like to use CocoaPods. Mugunth (original author of this framework) seems to be one of those: http://blog.mugunthkumar.com/articles/the-problem-with-cocoapods/
So I think there should be a way to use MKNetworkKit without CocoaPods.
The actual problem: If I try to build an archive I always create a generic Xcode archive, not an iOS App Archive (as intended).
Taking into account
http://stackoverflow.com/questions/10715211/cannot-generate-ios-app-archive-in-xcode
the problem is that headers are copied to public in the end of the build phase. Just moving those headers to project solves the issue. I can understand that there are very good reasons to copy those headers to public, but there must be a way to make both worlds happy, the one that uses CocoaPods and the one that does not :)
This is a follow up to the issue #95
This issue was basically closed with the comment: "Just use CocoaPods". As far as I know there are some developers out there, who do not like to use CocoaPods. Mugunth (original author of this framework) seems to be one of those: http://blog.mugunthkumar.com/articles/the-problem-with-cocoapods/
So I think there should be a way to use MKNetworkKit without CocoaPods.
The actual problem: If I try to build an archive I always create a generic Xcode archive, not an iOS App Archive (as intended). Taking into account http://stackoverflow.com/questions/10715211/cannot-generate-ios-app-archive-in-xcode the problem is that headers are copied to public in the end of the build phase. Just moving those headers to project solves the issue. I can understand that there are very good reasons to copy those headers to public, but there must be a way to make both worlds happy, the one that uses CocoaPods and the one that does not :)