We had the same issue in one of our projects. The problem was that our backend used a production key to sign the payload. But for StoreKit testing, you have to use the test key. To retrieve that key: Open your .storekit file in Xcode Go to Editor > Subscription Offers Key Copy the key and Key ID Use that key to sign your offers for the sandbox environment.

Are there any workarounds to redeem offer codes on macOS?

I have the same issue, but my account is logged in correctly, and I can download reports for all products but one. More specifically, it says: Access Restricted with bundle id: com.company.app.quicklook. Or com.company.app.widgets. It indicates crashes or other information related to our QuickLook and Widgets extensions that block crash logs from downloading. Did anyone face a similar issue?

Yes, we have multiple targets in our project. Specifically: two apps, two frameworks, widget extensions, and a bunch of test bundles. These warnings are not unique to a specific target and occur in various places in the project.

I set SWIFT_STRICT_CONCURRENCY to Complete, and the only warnings I get are the ones regarding _preview and _platform: .../SwiftUI.PreviewProvider:4:34: Main actor-isolated static property '_previews' cannot be used to satisfy nonisolated protocol requirement .../SwiftUI.PreviewProvider:5:34: Main actor-isolated static property '_platform' cannot be used to satisfy nonisolated protocol requirement .../SwiftUI.PreviewProvider:4:34: Main actor-isolated static property '_previews' cannot be used to satisfy nonisolated protocol requirement .../SwiftUI.PreviewProvider:5:34: Main actor-isolated static property '_platform' cannot be used to satisfy nonisolated protocol requirement I've seen these warnings in my main project, but as far as I know, they do not appear when building with Xcode 15. And still, no warnings related to key paths, as shown in the original post.

Hello Quinn! Thank you for your response. I cannot reproduce these warnings on a test project, which leads to the obvious conclusion that it is somehow related to the current code or project configuration. Can you give any clue or hint where to look for the source of those compiler warnings, or how can we narrow down the search? Thank you!