Compilation issues "Undefined symbol: _OBJC_CLASS_"

StevenMasini commented 1 year ago

New Issue Checklist

[x] I am not disclosing a vulnerability.
[x] I am not just asking a question.
[x] I have searched through existing issues.
[x] I can reproduce the issue with the latest versions of Parse Server and the Parse ObjC SDK.

Issue Description

Getting the following compilation errors.

Undefined symbol: _OBJCCLASS$_FBSDKAccessToken
Undefined symbol: OBJCCLASS$_FBSDKApplicationDelegate
Undefined symbol: _OBJCCLASS$_FBSDKSettings

Steps to reproduce

Compile a project that make use of Parse/FacebookUtils using any version between 1.9.1 to latest 1.9.3

Actual Outcome

Expected Outcome

No compilation errors.

Environment

XCode 14.0.0, any arm64 devices

Client

Parse ObjC SDK version: 1.9.1, 1.9.2, 1.9.3

Server

Parse Server version: N/A
Operating system: N/A
Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): N/A

Database

System (MongoDB or Postgres): N/A
Database version: N/A
Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): N/A

Logs

N/A

parse-github-assistant[bot] commented 1 year ago

Thanks for opening this issue!

🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

StevenMasini commented 1 year ago

Seems to be a pretty old issue tho https://stackoverflow.com/questions/64294415/build-error-with-parse-ios-sdk-and-facebook/73943043#73943043

mtrezza commented 1 year ago

We can merge a PR to fix this, but also see https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1663.

With your fix, can you add the Parse ObjC SDK via Pod without any issues? If so we should add Pod to the supported implementation methods in #1663.

StevenMasini commented 1 year ago

@mtrezza I will try to find some time this weekend to work on it. The one solution that truly matters nowadays is SPM. But lots of developers are still relying on Cocoapods for their projects.

I think it's possible to add Cocoapods as a solution to setup Parse ObjC SDK.

mtrezza commented 1 year ago

In general, if you want to invest your time into trying to add SPM, it would be better spent I think. There are some PRs already that you could build upon, they show that adding SPM works as a proof of concept.

mathieulb commented 1 year ago

Is this really about versions 1.9.1 thru 1.9.3, or actually 1.19.1 thru 1.19.3, which are the most recent ones ? But I have that problem with any 1.19.x, even 1.19.0... and I can't seem to install 1.18.0, for other reasons...

danipralea commented 1 year ago

@StevenMasini how did you fixed it? I have the same issue and it's just driving me crazy. I did everything and I can't get rid of it

StevenMasini commented 1 year ago

@danipralea You can point to my repo until #1666 gets merged.

Replace this line in your Podfile

pod 'Parse', :git => 'https://github.com/StevenMasini/Parse-SDK-iOS-OSX.git', :commit => '75ad3d3608cba0ecbc4142a64de871cf3f84f172'

It will point to this commit on my fork https://github.com/parse-community/Parse-SDK-iOS-OSX/pull/1666/commits/75ad3d3608cba0ecbc4142a64de871cf3f84f172

EDIT: Assuming you are using Parse 1.19.3

danipralea commented 1 year ago

thank you @StevenMasini that finally fixed it! 🙏 🙏

mtrezza commented 1 year ago

Thanks for confirming @danipralea , I'll go ahead and merge the PR.

mtrezza commented 1 year ago

🎉 This change has been released in version 1.19.4

parse-community / Parse-SDK-iOS-OSX