I'm trying to implement in app purchases and subscription management on the server depends on properties like a unique subscription_id and any changes to auto_renew_status with each notification. the docs say this information should be present in a notification body but when i get sandboxed response they are missing any potentially identifying top level properties (such as an auto_renew_adam_id if i understand that property correctly.) do i use the auto_renew_adam_id to identify a subscription? if so how do i go about testing it in the sandbox, or at all? https://developer.apple.com/documentation/appstoreservernotifications/responsebody

We are implementing in app purchases and trying to test notifications in the sandbox environment. Important application behavior depends on receiving almost all of the notification types. I have an endpoint in production but im seeing notifications come in a pattern i dont really understand. How can i test different types of notifications to make sure the app-store server is sending the kind of data I would expect based on the notification type? Any resources would be helpful as all i can find are a few threads that dont really address the question of how to use the sandbox environment to thoroughly test in app purchases. there are also some concerns about the reliability of these notification at present? Is it also advisable at this time to run background jobs to poll subscription status (ex nightly). or are there guarantees that these notifications will come eventually in production? Any help would be appreciated