Can you please revert back your changes to s.dependency 'Starscream', '~> 3.1.0' or better to s.dependency 'Starscream', '~> 3.1.1 ?
Because otherwise, if I use another 3'rd party dependency in my project like Cobrowse.io (which also requires Starscream) then I get pods conflicts error. In this case can't update ParseLiveQuery pod up to latest v2.7.2, because the following conflict error shown if I run pod update:
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "Starscream":
In snapshot (Podfile.lock):
Starscream (= 3.1.0)
In Podfile:
CobrowseIO/Extension was resolved to 2.8.8, which depends on
Starscream (~> 3.1.1)
ParseLiveQuery was resolved to 2.7.2, which depends on
Starscream (= 3.1.0)
Hello,
In your previous releases
<= v2.7.0
the file: https://github.com/parse-community/ParseLiveQuery-iOS-OSX/blob/2.7.0/ParseLiveQuery.podspechad the Starscream dependency like:
but in your release
v2.7.1
, see: https://github.com/parse-community/ParseLiveQuery-iOS-OSX/pull/226you guys changed it to:
NO
~>
in dependency line unfortunately.Can you please revert back your changes to
s.dependency 'Starscream', '~> 3.1.0'
or better tos.dependency 'Starscream', '~> 3.1.1
?Because otherwise, if I use another 3'rd party dependency in my project like Cobrowse.io (which also requires Starscream) then I get pods conflicts error. In this case can't update ParseLiveQuery pod up to latest
v2.7.2
, because the following conflict error shown if I runpod update
: