SDK Not compiling on Xcode 26 due to deprecation warnings

[BarMalka]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Describe the bug
Our project is configured with SWIFT_TREAT_WARNINGS_AS_ERRORS = YES.
When I was compiling our project in Xcode 26, under the current latest release (5.28.1) I am getting multiple deprecation errors (warnings). Here's a few:
'SKPaymentTransaction' is deprecated: first deprecated in iOS 18.0 - Use PurchaseResult from Product.purchase(confirmIn:options:)
'SKPaymentQueueDelegate' is deprecated: first deprecated in iOS 18.0 - No longer supported
'SKPaymentTransactionObserver' is deprecated: first deprecated in iOS 18.0 - Use StoreKit 2 Transaction APIs
See screenshot below

1. Environment
   1. Platform: iOS
   2. SDK version:
   3. StoreKit version:
      • StoreKit 1 (default on versions <5.0.0. Can be enabled in versions >=5.0.0 with .with(storeKitVersion: .storeKit1))
      • StoreKit 2 (default on versions >=5.0.0)
   4. OS version: 15.4 (24E247)
   5. Xcode version: 26.0 beta 1
   6. Device and/or simulator:
      • Device
      • Simulator
   7. Environment:
      • Sandbox
      • TestFlight
      • Production
   8. How widespread is the issue. Percentage of devices affected.
2. Debug logs that reproduce the issue. Complete logs with Purchases.logLevel = .verbose will help us debug this issue.

3. Steps to reproduce, with a description of expected vs. actual behavior

Please fill in

4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

5. Additional context
   Add any other context about the problem here.

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[ajpallares]

Hi! Thank you for opening the issue @BarMalka! This is Antonio from the CoreSDK team.

I tried to reproduce this scenario in a Sample app I created from scratch and I could only do it when adding purchases-ios as a XCFramework directly, but not when adding the dependency through Cocoapods or Swift Package Manager. Just to be sure, how are you adding the purchases-ios dependency?
If you're not using the XCFramework approach, I'll need some more information to be able to reproduce it. What version of macOS? Is your project Swift only or does it contain Objetive-C code as well?

[BarMalka]

Hi @ajpallares 👋🏻
Thanks for the update!
We are indeed using the framework as xcframework.
I used macOS 15.4 when I opened the ticket.
Now I'm running macOS Tahoe 26 beta 1.

Is there any additional information you need?

[ajpallares]

Thanks for the quick reply @BarMalka!

You're using XCFramework, which also reproduced it for me. So no more info needed. I was afraid that you were encountering the compilation issues with a different way to add the purchases-ios dependency.

Have you considered adding purchases-ios via Swift Package Manager? It could be a good temporary workaround until we find a way to remove the warnings.

[BarMalka]

Thanks @ajpallares
We can do workaround for now. I'm glad you guys are aware of the deprecation now and we'll be waiting for the fix 👍🏻

Thank you

[BarMalka]

@ajpallares Any news regarding this? We will need this fixed soon! 🙏🏻