In my case, I opened it in Keychain access and added it to the System keychain, where the older, expiring certificate currently resides. Install the new certificate from Apple.So what do we do? Fortunately, after chatting through the problem with some friends, Chris Liscio deduced the key, somewhat-obvious in retrospect steps to test your Mac app for compliance with the new certificate, while getting sandbox testing working again at the same time: The linked “pre-release version” was no-doubt once a valid link, but at least through my account, it now leads to a permission-denied type failure page. A pre-release version of the Mac App Store Update for OS X Snow Leopard beta is now available. You can verify your receipt validation code is compatible with the renewed certificate in the test and production environments.

Even though the page linked above has a section explicitly listing what Mac developers are expected to do: Still, the communication from Apple about this issue was poor enough that it wasn’t obvious what exactly we needed to do. But as time went on, it started to seem as though it could be related to Apple’s announcement that one of its key certificates was expiring. So here's what I'm getting on 10.11.2 when trying a sandbox MAS account: 'This Apple ID has not yet been used with the App Store.'Īt first, we assumed it was a bug. After updating to 10.11.2, many of us noticed that this functionality suddenly stopped working: Previously, a sandbox user account could be used to authenticate and download a _MASReceipt for a Mac app, to ensure that in-app receipt validation is working as expected. For months, many of us Mac developers have noticed that apps built for Mac App Store submission could no longer be tested using iTunes Connect “sandbox” users.

Apple sandbox certificate