-
-
Notifications
You must be signed in to change notification settings - Fork 133
Receiver type 'PFLiveQueryEvent' for instance message is a forward declaration (Xcode 12 Beta 6 / Objective-C project) #230
Comments
Xcode 11 converts the
where Xcode 12 does just
It feels like Apple has changed how code is converted and the |
Following up on @akmarinov investigations, I tried multiple code permutations but I couldn't find a sensible reason explaining why I tried to remove exposed properties, add new exposed methods, rename the class, shuffle code around, and so on… nothing seems to have any effect. Moving It looks like a weird compiler bug, so I'm going to open a radar. |
Hey @ephread! Any news about this issue? Regards, |
@vexelgray you can use @ephread 's workaround on this fork of the repo - https://github.com/combyne/ParseLiveQuery-iOS-OSX/commits/xcode-12 until it's addressed on the main repo.
|
@ephread Can you do a PR for this? Would love to include your fix for the community. |
@dplewis Absolutely, no worries. I'll create the PR some time this week. |
I'm having a rather strange issue. I'm not certain it's an problem with ParseLiveQuery, but before opening a radar I'd like to know if I'm the only one having the issue (I didn't find any reports matching the problem on OpenRadar).
On Xcode 12 beta 6, any time a
PFLiveQueryEvent
instance is accessed, the compiler is complaining. I think it extends to other types as well.I investigated a bit and can't see anything wrong in the codebase. Maybe someone will have better luck.
Here is a demo project, it's just the repo with all the dependencies pre-downloaded, Parse patched with parse-community/Parse-SDK-iOS-OSX#1527 and a couple of lines added to the example project. Just open
Examples/LiveQueryDemo-ObjC.xcodeproj
and try to build the macOS App. It should trigger the error right away. It's a bit big, so it's available here.Thanks for your help!
Edit: Xcode 12 GM just dropped, I'm going to check if the issue is still present.
Edit 2: Still happening with the GM, sadly.
The text was updated successfully, but these errors were encountered: