Posts

Post not yet marked as solved
5 Replies
979 Views
We have started seeing v2 notifications coming in - various types/subtypes - that contain a signedRenewalInfo JWT, but no signedTransactionInfo JWT. This is new, we haven't seen it before. What's happening, what do we do with these? Is this a bug or has there been a change to the spec? There is no expire date and other information that is needed to properly process subscription updates. According to your documentation, this is not supposed to happen: https://developer.apple.com/documentation/appstoreservernotifications/data Our code is written to expect the data structure described in the documentation, and has worked fine for a long time, but this is now causing errors; please advise us on what we are expected to do here.
Posted
by pnicoFP.
Last updated
.
Post not yet marked as solved
1 Replies
487 Views
We have some subscription items that we no longer offer for purchase directly in our app. We want to continue supporting them for users that already have them, unless/until they decide to try our new offering or end their subscription. But we do not want to be still offering them for purchase in iOS subscription settings. Is there a way for us to do this currently? If not, please provide a way to deprecate subscription items so users who do not currently subscribe to them will not be able to purchase them outside our app in subscription settings. If we were able to do this, it would give us a path to gracefully remove these subscriptions from sale. As it is, we are forced to decide between either supporting them forever or abruptly cutting them off for all the users that have them, neither of which are good options.
Posted
by pnicoFP.
Last updated
.