feat: Remove support for Xcode 14

[dplewis]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

The CI is currently broken due to simulators not being support across 3 versions of Xcode.

Closes: #1836

Approach

• Test against Watch 9
• Test against iPhone 16
• Test against Xcode 15 / 16

TODOs before merging

• Add tests
• Add changes to documentation (guides, repository pages, in-code descriptions)

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[dplewis]

@mtrezza Looks like there are 3 failing / flaky tests, the starter projects build correctly on Xcode 15/16

-[InstallationUnitTests testInstallationHasApplicationBadge]
-[InstallationUnitTests testInstallationSetsApplicationBadge]
-[ParseClientConfigurationTests testServerValidation]

[mtrezza]

Great, do you have any guesses why they are failing?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.65%. Comparing base (dd05d41) to head (b53dfa7).
Report is 39 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #1835       +/-   ##
===========================================
+ Coverage   64.24%   82.65%   +18.40%     
===========================================
  Files         201      282       +81     
  Lines       23233    30723     +7490     
===========================================
+ Hits        14926    25393    +10467     
+ Misses       8307     5330     -2977     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dplewis]

@mtrezza I disabled the tests for now but I kinda figured out what is wrong. There are currently 3 trackers for the app badges.

[PFApplication currentApplication].systemApplication.applicationIconBadgeNumber
[PFApplication currentApplication].iconBadgeNumber // don't need this as it's only tracking the badges, internal, not used in macos
PFInstallation.badge

https://github.com/parse-community/Parse-SDK-iOS-OSX/pull/1835/files#diff-dfe3d69d32126f73e0311c93db9c0dfa92d02c375a4360aaf6b089d153cd7fef

Will fix in a separate PR.

[mtrezza]

Great, is that a SDK bug you discovered or just a testing issue?

[dplewis]

I think it's a testing issue but could be a bug. I don't think it's safe to have an observer on applicationIconBadgeNumber which is deprecated just to update iconBadgeNumber. This observer is what's causing the tests to fail.

https://developer.apple.com/documentation/uikit/uiapplication/applicationiconbadgenumber?language=objc

[dplewis]

@mtrezza I opened a issue for 7f5da14

[dplewis]

@mtrezza This is ready for review

[mtrezza]

@mtrezza I opened a issue for 7f5da14

Good, could you reference the issue you opened here, so the discussion can be tracked?

[mtrezza]

I went back to individual jobs for LiveQuery, as it turned out that it's hard to debug in a combined test, and takes longer. Turns out that finding the right simulator settings to get the job working can take some time; that doesn't seem to be a code issue, but just how the simulator destination is set up. Instead of specifying the simulator by its ID we are selecting OS version and device model, which can be ambiguous, especially in watchOS <> iOS peering hence the test can easily fail because of the system OS / Xcode / simulator OS version compatibility.

[parseplatformorg]

🎉 This change has been released in version 5.0.0