You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you go to Alamofire's Cocoadocs page, you'll see there's an error parsing the pod. I ran into the same problem with my project, ForecastIO. The issue is that there are two .xcodeproj files at the root of the repo ("Alamofire.xcodeproj" and "iOS Example.xcodeporoj"). In order for Cocoadocs to properly generate docs for Alamofire, "iOS Example.xcodeproj" needs to be moved out of the root.
The text was updated successfully, but these errors were encountered:
It looks like Cocoadocs now supports .jazzy.yaml config files. Instead of moving the example project out of the root, you can add a jazzy config file that specifies which project should be used.
If you go to Alamofire's Cocoadocs page, you'll see there's an error parsing the pod. I ran into the same problem with my project, ForecastIO. The issue is that there are two .xcodeproj files at the root of the repo ("Alamofire.xcodeproj" and "iOS Example.xcodeporoj"). In order for Cocoadocs to properly generate docs for Alamofire, "iOS Example.xcodeproj" needs to be moved out of the root.
The text was updated successfully, but these errors were encountered: