Use 'Parse' instead of 'Parse-iOS-SDK'
Closed this issue · 6 comments
Parse-iOS-SDK and Parse-OSX-SDK has since been unified into one Pod. actually I'm not so sure of this ...!
Using Parse-iOS-SDK causes problems with other libraries that depend on Parse, e.g. https://github.com/futuraio/ParseModel-iOS/blob/master/ParseModel.podspec
I will look into this. There was a reason I chose Parse-iOS-SDK, as at one point it was just using Parse but I think there was a conflict or issue with the spec. Have you tried using Parse-iOS-SDK? Do you have any comment on why one should be used over the other? I'm just trying to get the full picture here and make an educated decision.
Thanks!
It appears there is another pod now... Parse-iOS as well. :P
Sorry yeah you're right. I made a premature decision myself before posting this issue.
Parse as it stands is more up-to-date.
I guess individual library maintainers cannot sensibly choose one over another — just choose what works. I think it's because Parse themselves haven't gotten around to officially supporting their own podspec. They should so get with the times!
I think we just have to wait it out. For now Parse-iOS-SDK works. I'll close the issue.
Okay — now Parse-iOS-SDK pod has been deprecated in favour of Parse. See CocoaPods/Specs#11294. This is still 'unofficial' (i.e. Parse are not the maintainers) but at least the community has consensus now. nikita from Facebook/Parse is the maintainer, so it's as official as it gets.
Please update when convenient!
Sounds good. I will update this later today.
Okay, I've pushed out v0.9.2. Let me know if you have any problems.
Thanks!
Awesome. 👍