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

docs(ios): fix 'FBSDKCoreKit/FBSDKCoreKit-swift.h' file not found on case-sensitive filesystems #458

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

Romick2005
Copy link
Contributor

This fix the issue for case-sensitive file systems.
It would have no impact for not case-sensitive user systems.

Build error:

image

Fix 'FBSDKCoreKit/FBSDKCoreKit-swift.h' file not found for case-sensitive file systems.
@stale
Copy link

stale bot commented Oct 13, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Oct 13, 2023
Copy link
Collaborator

@mikehardy mikehardy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice one! That is subtle, in so far as very few people use case-sensitive file systems for macOS but for those that do, this is very important. Thank you!

@stale stale bot removed the wontfix This will not be worked on label Oct 18, 2023
@mikehardy mikehardy changed the title Fix 'FBSDKCoreKit/FBSDKCoreKit-swift.h' file not found docs(ios): fix 'FBSDKCoreKit/FBSDKCoreKit-swift.h' file not found on case-sensitive filesystems Oct 18, 2023
@mikehardy mikehardy merged commit 36a762a into thebergamo:master Oct 18, 2023
1 check failed
Copy link

🎉 This PR is included in version 12.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants