-
-
Notifications
You must be signed in to change notification settings - Fork 872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in macOS project _OBJC_CLASS_$_PFProductsRequestHandler version 2.0.2 #1699
Comments
Thanks for opening this issue!
|
If you just want to get your project linking and surprise this link error, you can add a stub class to the project with the same name:
and
|
I have the same issue. It might be because Is there an easy way to ensure these unavailable files are not included in the Mac builds? I didn't have this issue when using CocoaPods, but now that we moved to SPM this occurred. |
Same issue here running MacBook Pro M2. |
This issue is still affecting my app. The interim fix suggested by @rogernolan has not worked for me. If I knew how to fix it in the parse code I would. Help! Anyone? |
This is so frustrating. |
Because of this error the whole Parse-SDK-iOS-OSX should drop the "OSX" from its name. It won't compile since February for Mac apps. |
@santiagoprieto I don't know why PFProduct isn't supported on Mac, probably because StoreKit didn't support Mac at the time of this SDK creation. Looks like it does now from MacOS 10.7+ and StoreKit 2 has been release. If you want to look into this you can add I've created a PR to fix this issue #1739 |
New Issue Checklist
Issue Description
Getting the following compilation errors
Parse-SDK-iOS-OSX added with SPM.
Errors only app for mac os application. Project for iOS App no compilation errors.
Steps to reproduce
Compile a new mac os project that make use of Parse-SDK-iOS-OSX version 2.0.1 or 2.0.2.
Actual Outcome
Expected Outcome
No compilation errors.
Environment
ObjC SDK version:
2.0.2
Mac OS - Ventura 13.0
Apple M1 Pro
Xcode - Version 14.2 (14C18)
Client
2.0.2
Server
N/A
N/A
N/A
Database
N/A
N/A
N/A
Logs
The text was updated successfully, but these errors were encountered: