Skip to content
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

Undefined Symbols _OBJC_CLASS_$_Parse #1771

Closed
spiderguy84 opened this issue Jan 24, 2024 · 4 comments
Closed

Undefined Symbols _OBJC_CLASS_$_Parse #1771

spiderguy84 opened this issue Jan 24, 2024 · 4 comments
Labels
type:question Support or code-level question

Comments

@spiderguy84
Copy link

spiderguy84 commented Jan 24, 2024

New Issue Checklist

Issue Description

Steps to reproduce

<Install parse, initializeWithConfiguration in AppDelegate>

Actual Outcome

Expected Outcome

Environment

<Xcode 15.1, macOS 14.1.1, >

Client

  • Parse ObjC SDK version: 2.7.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

<ld: Undefined symbols:
OBJC_CLASS$_Parse, referenced from:
in AppDelegate.o
OBJC_CLASS$_ParseClientConfiguration, referenced from:
in AppDelegate.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Copy link

parse-github-assistant bot commented Jan 24, 2024

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.

@JohnCaccavale
Copy link
Contributor

I seem to be having a similar issue with the macOS SDK today (along with about a hundred Double-quoted include "ParseHeader" in framework header, expected angle-bracketed instead warnings)

My MacOS command line app builds fine when I do a debug build and run. When I try to Archive a Release version of the utility, these errors then occur with Xcode 15.3 running on an Intel based Mac.

There does not seem to be anything out of the ordinary with regard to my Build Settings. Architectures set to ARCHS_STANDARD. Nothing specified for Excluded Architectures.

My logs are as follows.

ld: warning: ignoring file '/Users/John/Documents/MyProject/Parse/Bolts.framework/Versions/A/Bolts': found architecture 'x86_64', required architecture 'arm64'
ld: warning: ignoring file '/Users/John/Documents/MyProjectr/Parse/Parse.framework/Versions/A/Parse': found architecture 'x86_64', required architecture 'arm64'
Undefined symbols for architecture arm64:
"OBJC_CLASS$_PFObject", referenced from:
OBJC_CLASS$_MyClass in MyClass.o
OBJC_CLASS$_MyClass2 in MyClass2.o
in MyClass3.o
"OBJC_CLASS$_PFQuery", referenced from:
in SomeClass.o
"OBJC_CLASS$_Parse", referenced from:
in SomeClass.o
"OBJC_CLASS$_ParseClientConfiguration", referenced from:
in SomeClass.o
"OBJC_METACLASS$_PFObject", referenced from:
OBJC_METACLASS$_SomeClass in SomeClass.o
OBJC_METACLASS$_SomeClass in SomeClass.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Apr 27, 2024
@JohnCaccavale
Copy link
Contributor

@spiderguy84 are you still having this issue. I removed the prebuilt compiled framework from my project, re-added the framework via Swift Package Manager, and these issues went away for me.

@mtrezza
Copy link
Member

mtrezza commented Apr 27, 2024

@JohnCaccavale If the issue is resolved for you, then I'll go ahead and close it. In case @spiderguy84 reports back that the issue still exists, we can re-open.

@mtrezza mtrezza closed this as completed Apr 27, 2024
@mtrezza mtrezza added type:question Support or code-level question and removed type:bug Impaired feature or lacking behavior that is likely assumed labels Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:question Support or code-level question
Projects
None yet
Development

No branches or pull requests

3 participants