-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix Xcode Build issues by removing merge conflict leftovers from code #20
Fix Xcode Build issues by removing merge conflict leftovers from code #20
Conversation
Example output for
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Tracking Info
Make sure your branch name conforms to:
<feature|staging|bugfix|...>/<username>/<3-4 word description separated by dashes>
. Otherwise, please rename your branch and create a new PR.Looks like when merge conflict was resolved in commit d4bfb5c some lines like
main
got left in the codebase. This was causing a parse error when opening the project through xcode.Future note -
Running
xcodeproj show ALUM.xcodeproj
from terminal gives more details on what kind of error happened because of which XCode is not openingChanges
What changes did you make?
Testing
How did you confirm your changes worked?
Confirmation of Change