Skip to main content
Question

Expiration is not received immediately after cancellation event is triggered in IOS sandbox

  • November 1, 2024
  • 3 replies
  • 117 views

Forum|alt.badge.img+3

Hi! 
I work at an app that uses subscriptions. I implemented with revenue cat and I test using sandbox environment on iOS simulator. For communication with our backend I use web hooks. 
For The first subscription it triggers the INITIAL_PURCHASE event and at every five minutes it triggers the RENEWAL event. When I cancel the subscription it send the  CANCELLATION event but, it not send the EXPIRATION event at the following RENEWAL. Please explain me how it works the expiration event and how to send an expiration event web hook to test our integration. 
thanks

This post has been closed for comments

3 replies

joan-cardona
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 389 replies
  • November 5, 2024

Hi @agrocity-technologies-48a744,

I would recommend checking that you want to receive all webhooks and not specific ones in Events filter, if so make sure that the EXPIRATION event is marked. 

If that’s all correct and you are receiving the INITIAL_PURCHASE and RENEWAL webhooks in sandbox, it looks like you hit a sandbox limitation. While production and sandbox should work the same, the resources provided by the stores are limited and hence it’s possible that you are not receiving all webhooks or that the information is not fully correct. Even though it’s not ideal and I know it’s risky, I wouldn’t worry to much and I would check it in production.

If you want to test the EXPIRATION event, you can send a test webhook and check that everything looks good from your side.

Let me know if this works!


Forum|alt.badge.img+3
joan-cardona wrote:

Hi @agrocity-technologies-48a744,

I would recommend checking that you want to receive all webhooks and not specific ones in Events filter, if so make sure that the EXPIRATION event is marked. 

If that’s all correct and you are receiving the INITIAL_PURCHASE and RENEWAL webhooks in sandbox, it looks like you hit a sandbox limitation. While production and sandbox should work the same, the resources provided by the stores are limited and hence it’s possible that you are not receiving all webhooks or that the information is not fully correct. Even though it’s not ideal and I know it’s risky, I wouldn’t worry to much and I would check it in production.

If you want to test the EXPIRATION event, you can send a test webhook and check that everything looks good from your side.

Let me know if this works!

I set up to receive all webhooks, and in the tests, I receive the INITIAL_PURCHASE, RENEWAL, and CANCELLATION events, but only the EXPIRATION event is not received in the sandbox on IOS. Can it be a limitation of the IOS sandbox and in production to trigger the EXPIRATION webhook? 


joan-cardona
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 389 replies
  • November 11, 2024

Hi @agrocity-technologies-48a744,

I’ve checked the webhooks sent to your project and I can see EXPIRATION webhook events sent to your servers and successfully accepted. Check for example one which id ends in 4122de. You can see all the latest events we send in the integration menu and selecting webhooks inside the project.

At the same time I see that you have some failed ones in different integrations which I would recommend to check what’s going on to ensure the correct delivery of events.

Let me know if you have questions!

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings