I'm looking at possible return values when StoreKit's AppTransaction fails, and the same error domain is returned. I can find no documentation on this. Some of the failures return the helpful string "The operation couldn't be completed", and an ASDErrorDomain number.

Unfortunately not. I mentioned this in a post above. I've had a user who wound back to 15.2 and everything is now working, but that could be as a consequence of the clean slate caused by the install.

Yeah I know - I mean in production. That's why I said I can't test it except live, as in, already in the store. I see no other option, looking at the documentation on AppTransaction.shared and AppTransaction.refresh()

I've just added a post to this thread: https://developer.apple.com/forums/thread/773604 Very relevant. This stuff is murky. @Tlaloc I think I'm going to have to release a maintenance build and test its effectiveness live. Looks like I'll have to force users to call AppTransaction.refresh() I believe you've been here before? :) Now I come to think about it, I've seen other apps I've purchased ask me to confirm my credentials when they launch. This is contrary to Apple's guidelines on refresh(), which you are only supposed to do as a result of an informed action on the user's part, such as clicking a button.

FWIW, I had a user with this issue contact me this morning after installing 15.4.1, but unfortunately it didn't make the issue go away. For one fleeting moment my hopes rose...

I'm reading the above posts with interest. Having similar problems with macOS 15.4, and trying to decide what to do. It's impossible to test this behaviour without releasing maintenance builds and treating your userbase as live guinea pigs. Here's my recent post: https://developer.apple.com/forums/thread/780767

Our first frustrated 1* review has just landed. Over the last few years we've had nearly all 5* reviews. I suspect it won't be the last. But I'm not bitter... :) Perhaps I'll just pack in being a developer and do something else.

@Tlaloc well, first of all, a huge thanks for actually responding at all. I can't get anything out of Apple. I don't know what's going on with StoreKit 2, but testing it is not possible in development, it's so flakey (certainly on the mac, anyway). Here's a post I did on Transactions on the Mac: https://developer.apple.com/forums/thread/758315 It just doesn't work reliably. I'm left thinking I'm going to have to use my live userbase for tests - i.e. try something in code and release it, then see if it works. I've been a developer for over 40 years and I've worked with a huge range of technologies, but I've never been in this position before. I've been suggesting users download the app again from the store. I have a swathe of suggestions I've been offering, but nothing seems to work. I've even bought our own app, and am running 15.4, but so far it works for me. We also offer the app via our website, so I've been handing out free licenses to that version. Your problem sounds bad, but at least there are things to try, even if they aren't ideal. I currently have no way forwards short of Apple fixing something, and that's not a position I want to be in.

Update: DTS Case-ID: 13195882 FB Assistant: FB17249398

FWIW our app has been in the store since 2009, so it contains a mixture of all the languages Apple has supported over the years. The startup code is the old-fashioned main(), which then calls NSApplicationMain(). The bulk of the dispatching is written in Objective-C and Objective-C++. The grunt work is mostly done in C++, and the StoreKit integration is written in Swift5/SwiftUI. The latest build of the app (the one that's failing) has a Deployment Target of macOS 14.2 and was built with Xcode 16.0 I've run into issues before with Objective-C / Swift integration, and I'm wondering if similar issues are in play here.

Hi @Tlaloc. I've been reading your posts with interest because I'm having issues with AppTransaction and 15.4. If you get chance, would you take a quick look at my post here and see if you can shed any light on it: https://developer.apple.com/forums/thread/780767

Our app is failing some of our long-term users because of this issue and we currently don't have anywhere to go, short of changing our sales model. The number of users contacting us with this problem is ramping up. Any Apple Engineers around to offer any guidance? I will submit a bug report and instigate a DTS. Quinn, I'm guessing you are familiar with issues surrounding AppTransaction. I've seen you offer guidance relating to receipts and transaction history in other posts. I'd really appreciate your view on this, even if it's just to acknowledge the issue or suggest an approach to debugging it. Or do I have "too much f***ing perspective"... :) Sorry. I know it was a joke on your part... The same comments go to @endecotp and @Tlaloc Thanks in advance.

Did you get any answers to this elsewhere? We are using AppTransaction in our mac app, and it's started failing with the release of macOS 15.4 See my post here: https://developer.apple.com/forums/thread/780767

Thanks for the help endecotp. I found the issue: my source file was included in multiple target dependencies and one of them wasn't using the Swift compiler. Found it by looking at the build transcript. I'll see if I can get the member variable thing working now, and will post a solution. As is often the case, the problem wasn't where I thought it was :)

Seems like my problem is that I can't get the following to work: include/import the auto-generated Swift header in either my C++ header or my C++ source file (which is a *.mm file), but I CAN include it in Objective-C++ source (also *.mm) and header files. When in the latter files I can CMD click on the auto-generated header to open it. Anyone got any suggestions? FWIW In my project settings I have set the name of the auto-generated Swift header file to be consistent across all of the build types, so it's not a debug build file naming issue.