blob: afa55d3fecac2d8942c45643ba5b8b0da70b4e06 [file] [log] [blame]
"name": "Foo",
"version": "1.1.1",
"summary": "This is a iOS framework containing both objective c and swift code",
"description": "This is example cocoa pods of how iOS frameworks work in reality containing both Objective c and Swift code. The framework uses Modules to address the issues of accessing private objective C files within the swift ecosystem and still keeping those objective c Files private within the framework and not exposed to the end user. \n\nSome Known Issues which are fixed in iOS mixed frameworks \n\n1. Debugging Swift code within the framework : This is fixed naming the modules rightly\n2. Module not found issue when doing a POD install after you have fixed issue number 1 : After fixing issue 1 which is renaming the pods to canonical form would result in error on the client app using the POD which would be for example Module not found. But renaming rightly in this case \n 1. Foo.private.modulemap should have the module name as Foo_Privates\n 2. module.modulemap should have the module name as Foo_Private\n 3. Note : Both Foo_Privates and Foo_Privates are different names with a underscore to silent the warning : expected canonical name for private module. which then allows the debugging of swift code as expected.\n3. Test targets don’t work as expected and don’t have access to Swift or Objective c Code and vice versa \n4. The mixed iOS framework now has a test target written in swift, Which means you can now write your test cases in swift within a mixed framework environment. \n\nNote : Generally the above mentioned issues should be working be default within the apple ecosystem but unfortunately within a iOS framework things gets a bit complex than expected and using modules and following some right naming convention all of the above can successfully work.",
"homepage": "",
"license": "MIT",
"authors": {
"Deepesh": ""
"platforms": {
"ios": "11.0"
"source": {
"git": "",
"tag": "1.1.1"
"vendored_frameworks": "Foo/Foo.framework"