I asked Developer Technical Support some of these questions. The interesting parts of the replies were these: does this DeviceCheck APIs also validate 2 of the 3 above features i.e. app is not modified and the device is genuine apple device? They say: "(DeviceCheck and App Attest) are different elements you can use in your protection/anti-fraud policy. They target different aspects, DeviceCheck focuses on the device, and AppAttest focuses on the integrity of your app code." My understanding from that is that DeviceCheck does not check if the app is modified, but perhaps modifying the device is a necessary prerequisite to modifying the app. Can we get exhaustive list of cases where isSupported is false? I asked specifically about iOS apps running on macOS ("Designed for iPad"), and they say: "The issue on macOS 11 is a known bug that has since been fixed. Barring any bugs, isSupported() should return true for Apple Silicon Macs and newer models of Intel Macs (with Touch ID)."

will I be able to enroll for a developer program as XHALESOLUTIONS LIMITED Yes, if that is your business.  then launch my product app under the organization XHALESOLUTIONS LIMITED Yes.

No, that information is not in the receipt.

I asked Developer Technical Support about this, and they suggested that I should use "#ifdef DEBUG". I am not convinced that that is a sensible approach. (Surely people test non-debug build before shipping, right?) There is a stack overflow question about this: https://stackoverflow.com/questions/3426467/how-to-determine-at-run-time-if-app-is-for-development-app-store-or-ad-hoc-dist The most popular idea there is to inspect the embedded.mobileprovision file. Has anyone here done that?

@Claude31, poor as this forum is my experience is still that posts here get more attention than bug reports and more useful answers than technical support incidents. YMMV.

It's for anyone with < $1 million sales. Yes for organisations. Note sales not profit.

No.

The receipt does not include the currency or price paid. Why do you think you need this? You may need to change your business model to remove this requirement.

In that example, you have not declared main(). Every program must have a main(). So you get an error saying "undefined symbol main". This is exactly the same error that you would get on Linux.

"Tracking" means tracking from one app/website to another app/website, e.g. you post to a InstaFace saying "I want to buy shoes" and when you next visit TickBook you see lots of adverts for shoes - because you have been tracked from InstaFace to TickBook. It sounds to me like you don't have "tracking" in your app.

You're unlikely to get useful errors without posting the code that you're trying to compile.

Having updated my Mac, it's also failing on 12.3. Edit: or maybe it isn't failing anymore. Hmm. Anyone else have anything to share?

Hi @webcompanist, Still experiencing the "incorrectHash" issue today. I posted this thread when receipt validation was not working on macOS 11.0. At some point it got fixed by Apple, either in macOS 11.1 or in a server-side change around that time. Now, more than a year later, I believe that it may have stopped working again. Perhaps due to a macOS update. )Or maybe I have managed to screw up my code somehow.) In my development environment it seems to not work on macOS 12.2.1. Looking at my diagnostics, it may be not working for customers on macOS 12.2 and macOS 11.5 - but it's also possible that those diagnostics are coming from people with cracked apps. Can anyone else report whether they have app receipt validation working with iOS-on-macOS ("Designed for iPad") with newish versions of macOS?

I disagree with MobileTen. I don't think the page that he links to says anything about offloading. Offloading is a relatively new feature in iOS. If the identifierForVendor changed during offloading, many apps that predated offloading (including one of mine!) would have had problems as a result. I have not seen any such problems, which makes me think that the identifierForVendor does not change. But I could be wrong; users do not always report problems. Anyone else have any experience to share? (Of course the safe thing to do is to assume that it can change at any time.)

Yes, I'm also seeing this. I guess it is related to the widespread outages yesterday. (The status page is now showing all green, but those things are always optimistic!) I suggest waiting for a few days.