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.

Sign up for GitHub

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

Jump to bottom

Several files not found when including Parse using SPM on Xcode 16 #1793

Closed
bmueller opened this issue Jun 28, 2024 · 9 comments · Fixed by #1795
Closed

Several files not found when including Parse using SPM on Xcode 16 #1793

bmueller opened this issue Jun 28, 2024 · 9 comments · Fixed by #1795
Labels
bounty:sponsored Bounty is sponsored and managed by a 3rd party (Parse Bounty Program) bounty:$250 Bounty applies for fixing this issue (Parse Bounty Program) state:released Released as stable version type:feature New feature or improvement of existing feature

Comments

@bmueller
Copy link

New Issue Checklist

Issue Description

I have an existing project that includes Parse via SPM. It builds just fine on Xcode 15. But when I try to build the same project on the Xcode 16 beta, I get several "file not found" error messages (PFObjectFileCodingLogic, PFAsset, PFOfflineStore, BFTask+Private, and ParseClientConfiguration_Private). I tried creating a brand new project, added Parse via SPM, and got similar errors when trying to build on Xcode 16.

Steps to reproduce

Create a new project, add Parse via SPM, then try to build it on Xcode 16 beta.

Actual Outcome

The compiler complains that it can't find some files.

Expected Outcome

The project builds with no issues.

Environment

Xcode 16 beta 2.

Client

  • Parse ObjC SDK version: 4.1.0

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
@parse-github-assistant Parse GitHub Assistant
Copy link

parse-github-assistant bot commented Jun 28, 2024 •
edited
Loading

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.

@mtrezza mtrezza added the type:feature New feature or improvement of existing feature label Jun 28, 2024
@mtrezza mtrezza pinned this issue Jun 28, 2024
@mtrezza mtrezza closed this as completed Jun 28, 2024
@mtrezza mtrezza added type:feature New feature or improvement of existing feature state:duplicate Duplicate of already reported issue and removed type:feature New feature or improvement of existing feature labels Jun 28, 2024
@mtrezza mtrezza unpinned this issue Jun 28, 2024
@mtrezza mtrezza reopened this Jun 28, 2024
@mtrezza mtrezza removed the state:duplicate Duplicate of already reported issue label Jun 28, 2024
@mtrezza
Copy link
Member

mtrezza commented Jun 28, 2024 •
edited
Loading

Could this be related to #1792? @mman It's building for your with Xcode 16, apart from the subclassing issue you described in #1792, right? Or is this issue here a duplicate?

@bmueller
Copy link
Author

I did see the issue @mman raised and it seemed like it was building for him since he was using code to keep the app from crashing once it was run. Open question on whether he was using SPM to build his project, though.

Is it possible to add a bug bounty to this issue? Happy to pay to have this fixed quickly!

@mtrezza
Copy link
Member

mtrezza commented Jun 28, 2024 •
edited
Loading

@bmueller Sure, please see our Sponsored Bounty program.

@bmueller

This comment has been minimized.

Sign in to view
@mtrezza

This comment has been minimized.

Sign in to view
@bmueller

This comment has been minimized.

Sign in to view
@mtrezza

This comment has been minimized.

Sign in to view
@mtrezza mtrezza added bounty:$250 Bounty applies for fixing this issue (Parse Bounty Program) bounty:sponsored Bounty is sponsored and managed by a 3rd party (Parse Bounty Program) labels Jul 3, 2024
roostr pushed a commit to roostr/Parse-SDK-iOS-OSX that referenced this issue Jul 12, 2024
@syrupticious @roostr
fix: SPM build issues with Xcode 16 (issue parse-community#1793)
9f82f46 
parse-community#1793

There is an issue with the Package.swift file where it uses wildcard
globbing to refer to all the private header directories that should
be included when building.

It turns out that it was a mistake that Xcode ever supported wildcard
globbing in the first place, as described here:

https://forums.swift.org/t/recursive-headersearchpath/59769

To fix it, we are replacing the wildcard glob with a list of all
header directories.

This issue was first observed on Xcode 16.0.0 beta 1. I confirmed that
it now builds correctly on Xcode 16.0.0 beta 2.
@roostr roostr mentioned this issue Jul 12, 2024
Merged
2 tasks
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.1.1

@parseplatformorg parseplatformorg added the state:released Released as stable version label Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bounty:sponsored Bounty is sponsored and managed by a 3rd party (Parse Bounty Program) bounty:$250 Bounty applies for fixing this issue (Parse Bounty Program) state:released Released as stable version type:feature New feature or improvement of existing feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: SPM build issues with Xcode 16 roostr/Parse-SDK-iOS-OSX
3 participants
@bmueller @mtrezza @parseplatformorg