Thanks very much, you are absolutely correct. I will mark the original answer correctly.
In essence, JWT should be structured with the correct header and claims as in the docs. The remainder were implementation details on my end that I recently cleared.
Jwt {
header: JwtHeader { typ: 'JWT', alg: 'ES256', kid: 'keyIDHere' },
body: JwtBody {
iss: 'issuer-id-from-AppStoreConnect-KeysSection',
aud: 'appstoreconnect-v1',
iat: 1630030166,
exp: 1630033766,
nonce: '90516455-0a3a-4a40-a863-eab63c7359ac',
bid: 'com.bundle.id',
},
signingKey: '-----BEGIN PRIVATE KEY-----\n' +
'YOUR\n' +
'PRIVATE\n' +
'KEY\n' +
'HERE\n' +
'-----END PRIVATE KEY-----'
}
ic99s
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Los Angeles, CA
Post
Replies
Boosts
Views
Activity
the video talks about subscription notifications, doesn't address responding to a consumable was consumed
I found a video from WWDC2019 titled "In-App Purchases and Using Server-to-Server Notifications", watching now ...