Failure generating documentation — Could not parse version component #1682
Assignees
Labels
build
Issues related to builds and dependency management.
CarPlay
Bugs, improvements and feature requests on Apple CarPlay
documentation
Comments
1ec5
added
build
|
In CocoaPods 1.6.0-beta.1, I get this error instead: |
|
This is tracked upstream in realm/jazzy#970. |
|
that issue is quite old. how do we work around it? |
|
I’m looking into ridding this script of CocoaPods usage. |
|
A fix is upstream in realm/jazzy#1004. Until that fix lands and is released, check out that jazzy branch and apply this patch, which assumes your jazzy clone sits beside your mapbox-navigation-ios clone: diff --git a/scripts/document.sh b/scripts/document.sh
index 989debfe..97464fa5 100755
--- a/scripts/document.sh
+++ b/scripts/document.sh
@@ -44,7 +44,7 @@ perl -pi -e "s/\\$\\{MINOR_VERSION\\}/${MINOR_VERSION}/" "${README}"
echo "## Changes in version ${RELEASE_VERSION}" >> "${README}"
sed -n -e '/^## /{' -e ':a' -e 'n' -e '/^## /q' -e 'p' -e 'ba' -e '}' CHANGELOG.md >> "${README}"
-jazzy \
+../jazzy/bin/jazzy \
--podspec MapboxNavigation-Documentation.podspec \
--config docs/jazzy.yml \
--sdk iphonesimulator \Despite finally getting docset output, there is still a mountain of warnings about symbols without USRs. Effectively, none of the conditionally compiled declarations are making it into the docset, because 491 warnings |
|
CocoaPods stubbornly refuses to generate an Xcode project that uses the iOS 12.0 SDK. It insists on using the iOS 10.3 SDK. That excludes any class with iOS 12 availability attributes, including every class in the CarPlay support code. Moreover, the iOS 10.3 SDK lacks CarPlay.framework, so any |
|
CocoaPods is using the hard-coded default iOS SDK version, which was last updated in CocoaPods/Xcodeproj#564 to be 11.3 as of CocoaPods 1.6-beta.1. Unfortunately, it isn’t possible to override the
By the way, this turned out to be infeasible due to a couple issues, including MapboxCoreNavigation and MapboxNavigation sharing several files. |
|
After trying unsuccessfully to hack around CocoaPods/CocoaPods#7972, I tried fixing #1682 (comment) the right way in CocoaPods/Xcodeproj#609 and pulling it into my local jazzy installation using Unfortunately, now that the generated Pod.xcodeproj refers to a real CarPlay.framework in the iOS 12 SDK, I’m hitting another roadblock: nothing declared with an realm/jazzy#11 tracks frontend support for
|
Merged
|
Fixed in #1714. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running scripts/document.sh with Xcode 10, CocoaPods 1.5.3, and jazzy 0.9.3 fails with the following build error. This is the same issue as mapbox/mapbox-directions-swift#292, but the fix in mapbox/mapbox-directions-swift#293 isn’t feasible here because we need CocoaPods to glom together the CoreNavigation and MapboxNavigation modules.
This issue needs to be fixed in time for the release that includes CarPlay support.
/cc @mapbox/navigation-ios
The text was updated successfully, but these errors were encountered: