Parse-SDK-iOS-OSX v1.13.0 is forcing dependency on Bolts ~>1.6 instead of Bolts ~>1.7

[marcosjvivar]

After doing a pod install with the following Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'

inhibit_all_warnings!
use_frameworks!

pod 'JSQSystemSoundPlayer', '4.3.0'
pod 'DateTools', '1.7.0'
pod 'Parse', '1.13.0'
pod 'FBSDKCoreKit', '4.13.0'
pod 'FBSDKLoginKit', '4.13.0'
pod 'FastEasyMapping', '1.0.2'
pod 'AFNetworking', '2.6.3' #3.0.4 available
pod 'AFNetworkActivityLogger', '2.0.4'
pod 'AsyncBlockOperation', '1.0.1'
pod 'Firebase', '2.5.1'
pod 'RNCryptor', '4.0.0'
pod 'BlocksKit', '2.2.5'
pod 'SDWebImage', '3.7.5'
pod 'FastImageCache', '1.5.1'
pod 'UICKeyChainStore', '2.1.0'
pod 'MXParallaxHeader', '0.5.0'
pod 'Analytics', '~> 3.0'
pod 'Segment-Mixpanel'

I read the Podfile.lock to see which version dependency I had for every pod and I see that Parse is using Bolts ~>1.6 when in its .podspec file it says s.dependency 'Bolts/Tasks', '~> 1.7'.

cat Podfile.lock

PODS:
  - AFNetworkActivityLogger (2.0.4):
    - AFNetworking/NSURLConnection (~> 2.0)
    - AFNetworking/NSURLSession (~> 2.0)
  - AFNetworking (2.6.3):
    - AFNetworking/NSURLConnection (= 2.6.3)
    - AFNetworking/NSURLSession (= 2.6.3)
    - AFNetworking/Reachability (= 2.6.3)
    - AFNetworking/Security (= 2.6.3)
    - AFNetworking/Serialization (= 2.6.3)
    - AFNetworking/UIKit (= 2.6.3)
  - AFNetworking/NSURLConnection (2.6.3):
    - AFNetworking/Reachability
    - AFNetworking/Security
    - AFNetworking/Serialization
  - AFNetworking/NSURLSession (2.6.3):
    - AFNetworking/Reachability
    - AFNetworking/Security
    - AFNetworking/Serialization
  - AFNetworking/Reachability (2.6.3)
  - AFNetworking/Security (2.6.3)
  - AFNetworking/Serialization (2.6.3)
  - AFNetworking/UIKit (2.6.3):
    - AFNetworking/NSURLConnection
    - AFNetworking/NSURLSession
  - Analytics (3.0.7)
  - AsyncBlockOperation (1.0.1)
  - BlocksKit (2.2.5):
    - BlocksKit/All (= 2.2.5)
  - BlocksKit/All (2.2.5):
    - BlocksKit/Core
    - BlocksKit/DynamicDelegate
    - BlocksKit/MessageUI
    - BlocksKit/UIKit
  - BlocksKit/Core (2.2.5)
  - BlocksKit/DynamicDelegate (2.2.5)
  - BlocksKit/MessageUI (2.2.5):
    - BlocksKit/Core
    - BlocksKit/DynamicDelegate
  - BlocksKit/UIKit (2.2.5):
    - BlocksKit/Core
    - BlocksKit/DynamicDelegate
  - Bolts (1.7.0):
    - Bolts/AppLinks (= 1.7.0)
    - Bolts/Tasks (= 1.7.0)
  - Bolts/AppLinks (1.7.0):
    - Bolts/Tasks
  - Bolts/Tasks (1.7.0)
  - DateTools (1.7.0)
  - FastEasyMapping (1.0.2)
  - FastImageCache (1.5.1)
  - FBSDKCoreKit (4.13.0):
    - Bolts (~> 1.7)
  - FBSDKLoginKit (4.13.0):
    - FBSDKCoreKit
  - Firebase (2.5.1)
  - GDCoreDataConcurrencyDebugging (0.1):
    - JRSwizzle
  - JRSwizzle (1.0)
  - JSQSystemSoundPlayer (4.3.0)
  - Mixpanel (2.9.9):
    - Mixpanel/Mixpanel (= 2.9.9)
  - Mixpanel/Mixpanel (2.9.9)
  - MXParallaxHeader (0.5.0)
  - Parse (1.13.0):
    - Bolts/Tasks (~> 1.6)
  - Reveal-iOS-SDK (1.6.2)
  - RNCryptor (4.0.0)
  - SDWebImage (3.7.5):
    - SDWebImage/Core (= 3.7.5)
  - SDWebImage/Core (3.7.5)
  - Segment-Mixpanel (1.0.3):
    - Analytics (~> 3.0.0)
    - Mixpanel (~> 2.9.0)
  - UICKeyChainStore (2.1.0)

I made a pod cache clean --all with a following pod deintegrate PROJECT.xcodeproj and a brand new pod install but I'm still seeing Bolts ~>1.6.

Is this on purpose or is it conflicting with Carthage's Bolts dependency, which is pointing to the ~>1.6 version?

[nlutsenko]

Hey @mvivardevspark,

~>1.6 means version at 1.6 and any version up to 2.0, but not including 2.0.
If you run pod update - does it change anything?

[marcosjvivar]

If I run pod update nothing happens. Bolts version stays in 1.6

[nlutsenko]

1.14 is coming soon (hope I can get to it this week), where this is going to be fully resolved.
Sorry for keeping you waiting, but the good news that the fix is coming!