#Install swift material ios pod install#
#Install swift material ios pod update#
#Install swift material ios pod upgrade#

#Install swift material ios pod upgrade#

NOTE: If instead of cocoapods 1.7.X we upgrade to just cocoapods 1.6.x, then xcodeproj gem will raise to version 1.8.X Why xcodeproj decides to add this attribute (with a value of 5.0) inside Pods.project, when in the past (Xcodeproj version 1.5.6 for example), it left this as РІР‚СљundefinedРІР‚Сњ? Particularly when we had never installed Xcode 10.2.X in these machines weРІР‚в„ўre running РІР‚Сљpod installРІР‚Сњ The РІР‚Сљpod installРІР‚Сњ action (having deleted РІР‚СљPodsРІР‚Сњ folder and РІР‚СљPodfile.lockРІР‚Сњ file beforehand) recreates a Pods.project file, but with SWIFT_VERSION attribute set to РІР‚Сљ5.0 (unsupported)РІР‚Сњ.

Having the latest versions of all these additional cocoapods related gems installed leads to the following (undesired for us) situation: Typically, once you have cocoapods 1.4.0 (and 1.6.0, 1.6.1, 1.7.0 and 1.7.1) you end up with things like, more than one fourflusher version installed (2.0.1, 2.2.0), more than one cocoapods version installed (logically), and more than one xcodeproj version installed (typically 1.5.6, 1.8.X and 1.9.0). What does it mean? Installing different CocoaPods versions also leads to additional gem installations in the background, mainly РІР‚СљfourflusherРІР‚Сњ, РІР‚СљxcodeprojРІР‚Сњ, etc.

#Install swift material ios pod install#

So far, weРІР‚в„ўve described the expected situation we would like to be dealing with, but some weeks ago we started to notice strange things when we needed to check our solution against different (newer) versions of РІР‚СљCocoapodsРІР‚Сњ (and its РІР‚СљsatelliteРІР‚Сњ associated gems).Р”В¬ocoapods is a piece of our toolkit that needs to be periodically checked, so in some machines we also started to install additional cocoapods versions (1.6.0, 1.6.1, 1.7.0 and 1.7.1) apart from our certified 1.4.0 When we do this, the expected (and wanted) result for our project is РІР‚СљundefinedРІР‚Сњ. If we browse this Pods.project from within Xcode we can look for the РІР‚СљSWIFT_VERSIONРІР‚Сњ keyword. This Pods.project is the big РІР‚СљumbrellaРІР‚Сњ where all the imported frameworks will live in our big solution. This pod install checks all our РІР‚Сљbrother projectsРІР‚Сњ repositories and it downloads whatever new internal pods it needs, and (here comes the important part), it recreates the РІР‚СљPodsРІР‚Сњ project (that means it recreates the Pods.project file).

#Install swift material ios pod update#

The last certified versions weРІР‚в„ўre dealing with are: Swift 4.0 + Xcode 10.1 + CocoaPods 1.4.0 (yes, we know CocoaPods 1.7.1 is out, but our validation process forces us to still work with 1.4.0).Р”Р„nyway, what does it all mean? It means when weРІР‚в„ўre developing our code, we need to update our internal libraries dependencies, situation which typically is resolved with a good old РІР‚Сљpod installРІР‚Сњ. Our architectural solution has to cover a range of versions of iOS/Swift/Xcode for it to be deployed. (It will be a crossposting doubt in stackoverflow/CocoaPods github). Part of the core of this solution needs CocoaPods and right now weРІР‚в„ўre very happy about all the complex module definition weРІР‚в„ўve created so far.Р”В«ut we have isolated an issue we donРІР‚в„ўt know if itРІР‚в„ўs a feature, a bug, a known factРІР‚В¦ WeРІР‚в„ўll describe it here with as much detail as we can, to see if someone can shed some light on it IРІР‚в„ўm part of a team developing some architectural iOS solution involving integrating private iOS frameworks.