Error with update to Parse 1.14.5

[loxx123]

Seeing errors now with Parse Live Query with update to Parse 1.14.5

duplicate interface definition for class 'PFEncoder'
duplicate interface definition for class 'PFPointerOrLocalIdObjectEncoder'
duplicate interface definition for class 'PFNoObjectEncoder'
duplicate interface definition for class 'PFPointerObjectEncoder'
definition of 'PFEncoder' must be imported from module 'Parse.PFEncoder' before it is required
could not build Objective-C module 'ParseLiveQuery'

[flovilmart]

yes it makes sense, as the encoders are now exposed directly from parse-iOS-SDK. I probably should have released it as a breaking change on the iOS side.

[loxx123]

Yep, exactly, I just rolled back to last Parse for now until I have a chance to take a look at reworking code.

…

Sent from my iPhone

On Jun 26, 2017, at 8:59 PM, Florent Vilmart ***@***.***> wrote: yes it makes sense, as the encoders are now exposed directly from parse-iOS-SDK. I probably should have released it as a breaking change on the iOS side. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[flovilmart]

I've unpublished the 1.14.5 version a new 1.15.0 will follow, which is semantically more correct.

[loxx123]

Perfect

…

Sent from my iPhone

On Jun 26, 2017, at 9:25 PM, Florent Vilmart ***@***.***> wrote: I've unpublished the 1.14.5 version a new 1.15.0 will follow, which is semantically more correct. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[CiraciNicolo]

Still broken, removing the bridging header seems to fix this because new version of Parse expose that class.

[flovilmart]

@CiraciNicolo, can you give more details please?

[flovilmart]

Ah right, we need a new version of the LQ SDK so it’s compatible with the latest parse-iOS-SDK now that it’s been released. I’ll craft one ASAP

[CiraciNicolo]

Using latest version via Carthage give the errors reported by @larceneaux because in the latest version the Parse iOS SDK export the classes above. Removing the bridging header and the redefinition of the class fix the problem building the project as standalone. I'm still unable to include this library in a complex project.

[flovilmart]

Do you set the version on Carthage? Or just use master?

[CiraciNicolo]

I'm using the master, github "parse-community/ParseLiveQuery-iOS-OSX".

[flovilmart]

that's why, you should probably use the latest tagged version (2.0.0), that's the reason we use semver

[flovilmart]

Why don’t you pin parse-iOS-SDK? Using master is dangerous

[CiraciNicolo]

Using the tagged version makes carthage fail. My Cartfile is

github "BoltsFramework/Bolts-Swift"
github "parse-community/Parse-SDK-iOS-OSX"
github "parse-community/ParseLiveQuery-iOS-OSX" ~> 2.0.0
<Other packages not Parse dependent/dependencies>

And the output of carthage update --platform iOS is like this:

*** Fetching Parse-SDK-iOS-OSX
*** Fetching Bolts-Swift
*** Fetching Bolts-ObjC
*** Fetching Starscream
*** Fetching Parse-SDK-iOS-OSX
*** Checking out Bolts-Swift at "1.3.0"
*** Checking out ParseLiveQuery-iOS-OSX at "2.0.0"
*** Checking out Starscream at "2.0.3"
*** Downloading Parse-SDK-iOS-OSX.framework binary at "1.15.0"
*** Checking out Parse-SDK-iOS-OSX at "1.15.0"
*** Checking out Bolts-ObjC at "1.8.4"
*** Downloading Parse-SDK-iOS-OSX.framework binary at "1.14.2"
*** Checking out Parse-SDK-iOS-OSX at "1.14.2"
A shell task (/usr/bin/env git submodule --quiet update --init --recursive (launched in /Users/<redacted>/Carthage/Checkouts/Parse-SDK-iOS-OSX/Vendor/xctoolchain)) failed with exit code 1:
fatal: Unable to read current working directory: No such file or directory
fatal: /usr/local/Cellar/git/2.13.2/libexec/git-core/git-submodule cannot be used without a working tree.

Parse-SDK is referenced 2 times with 2 different versions.

[flovilmart]

why don't you force Parse-SDK-iOS-OSX at "1.14.2" ?

[CiraciNicolo]

I've already tried, I get the same error as before.