Server to server Notificaitons

Question

Created Aug ’21

Replies 1

Boosts 0

Participants 2

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

Boost

Answer 1

elliancarlos OP

Jan ’22

We are also implementing in-app purchases in my team. As far as we've tested notifications can only be triggered by the mobile application (e.g. buying a product) or the apple store (e.g. change the renewal status of a subscription).

"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?"

As far as we've known you can only test this simulating user behavior. I would advise using the sandbox environment while testing.

"There are also some concerns about the reliability of these notifications at present?"

I don't think there is a concern about the reliability of these notifications, but apple does retry when your server does not respond with success (HTTP 200 OK).

I would not suggest running a background job to poll subscription status, I think you should rely on subscriptions and keep the receipt of the purchases in case of a catastrophic event. But, daily checking for the status of subscriptions was a strategy in the past, before notifications.

0