Suppress storekit violations in Xcode 26 #46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ecito
approved these changes
Sep 11, 2025
JoeSzymanskiNoom
approved these changes
Sep 11, 2025
|
Any update on merging an releasing this fix? It's blocking us from updating to Xcode 26. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference
SDK-XXXX -- <TITLE>.
Summary
Suppressed StoreKit Violations in the Xcode 26 beta.
I do not know if this is the correct way to fix this , i.e. if the storekit 1 apis are generally still in use. However, it does remove the warnings.
Motivation
When compiling in Xcode 26, with warnings-as-errors, you will be unable to compile, even if your app has a target SDK lower than iOS 26.
Type Of Change
Testing Instructions
cc @BranchMetrics/saas-sdk-devs for visibility.