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

[bmueller]

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

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[bot]]

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]

Could this be related to https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/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]

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]

@bmueller Sure, please see our Sponsored Bounty program.

[bmueller]

@mtrezza ok cool, so if I contribute via the "sponsor" button, how do I then get that applied to this issue? I didn't see an option for that on the sponsorship page. Also, I'd be happy to pay an additional amount if someone could get this addressed this week so I don't have to wait to continue work on my project - is there a mechanism to pay a bonus after the fact?

[mtrezza]

@bmueller For more info and to set up a sponsored bounty, please get in touch via our Slack.

[bmueller]

@mtrezza sounds great, how can I get an invite to the workspace?

[mtrezza]

It's open to anyone; I've added the Slack/Chat badge to the README, it was missing. Just click on it and get in touch.

[parseplatformorg]

🎉 This change has been released in version 4.1.1