macOS Store Kit

[Senor Cuete]

I was going to upgrade my receipt validation code to the newer Store Kit API. Reading the documentation I see that the types and methods used are described but not the headers that have their definitions. What .h files should I #import so that for example, the compiler knows what an AppTransaction is? Also some of the code in the documentation is in Swift only. Are these APIs available only with Swift?

Adding StoreKit.framework in Link Binaries With Libraries doesn't help.

Linking against AppKit.framework doesn't help either.

 

[Senor Cuete]

I guessed that linking against StoreKit.framework and #importing <StoreKit/StoreKit.h> would be the way to go. The project builds like this but the compiler thinks that AppTransaction, VerificationResult, etc. are undeclared identifiers.

 

[mfram]

I would look at the header files themselves to see what they say. I don't see anything about an "AppTransaction" in those header files.

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/StoreKit.framework/Versions/A/Headers

 

[prime17569]

The new StoreKit 2 APIs are designed for use with Swift and it doesn't seem like they can be used with Objective-C.

Using StoreKit 2 is not possible with Objective-C or if you need to support versions before iOS 15.0.

StoreKit 1 vs 2: How to Migrate to StoreKit 2

StoreKit 1 vs 2 & why the RevenueCat team has been hard at work to support StoreKit 2: a new Swift-only framework with modern async APIs.

www.revenuecat.com

 

[Senor Cuete]

Apple also dropped support for SSL and deprecated ASN.1. This makes it much harder to implement receipt validation, which was extremely difficult anyway due to (deliberately) incomplete, documentation. Replacing the ASN.1 functions like SecAsn1Decode() won't be very hard, but this is a step toward the day when programming the Mac will be Swift only. You can also expect to see them deprecate things like .xib files. This is ********.

 

[prime17569]

Apple also dropped support for SSL

They want you to use TLS 1.3 or newer now. TLS 1.2 is still supported, but it's not recommended. https://developer.apple.com/news/?id=bv8ur34d

and deprecated ASN.1.

They really want you to use the new StoreKit 2 API. See this thread: https://developer.apple.com/forums/thread/694197

Unfortunately, you will probably have to build some kind of shim that lets you communicate with StoreKit 2 from your objective-C code. Or rewrite your in-app purchase code in Swift.

You can also expect to see them deprecate things like .xib files.

Storyboards, nibs, xibs, and Interface Builder are already deprecated on visionOS. It's only a matter of time before this is the case on the other platforms.

 

[Senor Cuete]

I'm responsible for a big program written in Objective C with .xibs. When this is deprecated I'll quit programming the Mac. You mention writing some sort of shim to communicate between Objective C code and Swift. How difficult is it to mix Objective C/C and Swift?

 

[prime17569]

It is a bit complicated, but Apple provides some pointers here:

Importing Swift into Objective-C | Apple Developer Documentation

Access Swift types and declarations from within your Objective-C codebase.

developer.apple.com

 

[Senor Cuete]

Thanks for your help. I have a bunch of C code that performs complex mathematical calculations where high speed is required. I can't believe that Apple would deprecate the use of this in building applications.